workflow-foundation-to-design

workflow-foundation-to-design is a command for Claude Code from product-on-purpose/pm-skills. It costs 15 tokens per session (471 once invoked), scanned A, original, Apache-2.0.

An end-to-end workflow connecting a Foundation Sprint, used for strategic alignment, with a Design Sprint, used to prototype and test ideas with users. It carries the main hypothesis and highest-risk assumptions from the first sprint into the second.

In plain words
What is it for?
Use it to run the Foundation Sprint, identify the founding hypothesis and risky assumptions, then use them to frame Design Sprint readiness, questions, and prototype-validation work.
Why use it?
It provides a shared seven-to-eight-day path from deciding what to investigate to preparing and testing a design, without requiring a separate handoff document.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the pm-skills plugin — 69 skills, 11 commands, 6 agents, 2 hooks shipped together

Good fit Use it to run the Foundation Sprint, identify the founding hypothesis and risky assumptions, then use them to frame Design Sprint readiness, questions, and prototype-validation work.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/product-on-purpose/pm-skills/workflow-foundation-to-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/product-on-purpose/pm-skills

Made for: Claude Code.

Or install pm-skills, the plugin that ships this one along with the rest of its 69 skills, 11 commands, 6 agents, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for workflow-foundation-to-design

README.md
[![agentmods](https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-foundation-to-design/github.svg)](https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-foundation-to-design)
Your own site
<a href="https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-foundation-to-design"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-foundation-to-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for workflow-foundation-to-design

Your own site · 80×15
<a href="https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-foundation-to-design"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-foundation-to-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00471
Opus 5 $0.00008 $0.00235
Sonnet 5 $0.00003 $0.00094
Haiku 4.5 $0.00002 $0.00047

Measured 11d ago against content hash 50b9e1226305, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

workflow-foundation-to-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/workflow-foundation-to-design.md · 30 lines

How it starts

The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run the end-to-end arc that pairs a Foundation Sprint (2 days of strategic alignment) with a Design Sprint (5 days of prototype validation) as one connected 7-8 day flow.

There is no bridge skill: canonical Knapp/Zeratsky methodology has no formal handoff move between the two sprints, and pm-skills does not invent one. The Founding Hypothesis from the Foundation Sprint is consumed directly as input context by the Design Sprint readiness and brief steps; the handoff is narrative only.

Workflow Steps

Step 1: Foundation Sprint (Days 1-2)

Run the full Foundation Sprint using the /workflow-foundation-sprint command (or follow skills/tool-foundation-sprint-readiness/SKILL.md through skills/tool-foundation-sprint-founding-hypothesis/SKILL.md in sequence). Output: a canonical Founding Hypothesis sentence plus an assumption scorecard.

Step 2: Narrative handoff

Carry the Founding Hypothesis and its highest-risk assumptions forward as the framing context for the Design Sprint. No intermediate artifact is required: the riskiest assumption on the scorecard typically becomes the Design Sprint's challenge and sprint questions. See docs/guides/using-foundation-sprint.md and docs/guides/using-design-sprint.md for the handoff narrative.

Step 3: Design Sprint (Days 3-8)

Run the full Design Sprint using the /workflow-design-sprint command (or follow skills/tool-design-sprint-readiness/SKILL.md through skills/tool-design-sprint-test-and-score/SKILL.md in sequence), seeding the readiness and brief steps with the Founding Hypothesis from Step 1. Output: the Decider's build / iterate / pivot / stop call grounded in five customer interviews.

Output

A strategic frame (Founding Hypothesis) validated or invalidated end-to-end by a tested prototype and a Decider's call, in one connected arc.

Reference the end-to-end workflow at _workflows/foundation-to-design.md for the full narrative, including the handoff guidance.

Context from user: $ARGUMENTS

Read the full file on GitHub · 30 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 30 lines · 15 tokens per session scan A 50b9e1226305

Subscribe to this mod's changes

workflow-foundation-to-design is a command published in the GitHub repository product-on-purpose/pm-skills (658 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 471 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.