Agent skill

tool-foundation-sprint-approach-options

Day 2 morning move of a Foundation Sprint. Forces generation of 3 to 7 candidate approaches as one-page summaries before the team converges on a top bet. Use after Day 1 is signed and before Magic Lenses on Day 2 afternoon. Enforces a minimum of 3 approaches to prevent first-idea anchoring. Each approach summary names what it is, why it serves the differentiators, and includes a simple visual.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-approach-options --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.0.0
Declared author: product-on-purpose
Path: skills/tool-foundation-sprint-approach-options/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Foundation Sprint Approach Options Day 2 morning of a Foundation Sprint. The team forces itself to generate multiple plausible approaches before committing to one. The skill enforces a minimum of 3 approaches; anchoring on a single approach is the most common Day 2 failure mode. Family contract: [`docs/reference/skill-families/foundation-sprint-skills-contract.md`](../../docs/reference/skill-families/foundation-sprint-skills-contract.md). This skill is a member of `foundation-sprint-skills`. ## When to Use - Day 2 morning of a Foundation Sprint. - Day 1 is signed; the Mini Manifesto, decision principles, and differentiation chart are committed. - The team is ready to generate candidate approaches before evaluating them through Magic Lenses in the afternoon. ## When NOT to Use - Day 1 is unresolved. Approach Options without differentiation context produces approaches that miss the strategic position. - The team has only one approach in mind and is unwilling to generate alternatives. The skill forces minimum 3; if the team refuses, the issue is sprint discipline, not tooling. - More than 7 approaches

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. What This Skill Produces
  4. Sequence (75 minutes)
  5. Step 1: Frame the approach space (5 min)
  6. Step 2: Silent ideation (15-20 min)
  7. Step 3: Cluster and select 3-7 (15-25 min via Decider call)
  8. Step 4: One-page summarize each approach (25-40 min)
  9. Step 5: Cross-summary review (5-10 min)
  10. Approach Generation Discipline
  11. Inference Inputs
  12. Common Pitfalls
  13. Decider Role
  14. Canonical Sources
Ships with 3 files
  • HISTORY.md
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
What does the tool-foundation-sprint-approach-options skill do?

Day 2 morning move of a Foundation Sprint. Forces generation of 3 to 7 candidate approaches as one-page summaries before the team converges on a top bet. Use after Day 1 is signed and before Magic Lenses on Day 2 afternoon. Enforces a minimum of 3 approaches to prevent first-idea anchoring. Each approach summary names what it is, why it serves the differentiators, and includes a simple visual.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-approach-options --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going