Tool Foundation Sprint Approach Options

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2abfbb961d31 · 19 Oct 2026Report an issue or request a re-scan

• Publisherproduct-on-purpose GitHub organizationOwner of the repository this skill is read from
• Source folderproduct-on-purpose/pm-skills/skills/tool-foundation-sprint-approach-optionsThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict2abfbb961d31A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: tool-foundation-sprint-approach-options
description: 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.
license: Apache-2.0
metadata:
  classification: tool
  version: "1.0.0"
  updated: 2026-07-04
  tool: foundation-sprint
  move: approach-options
  category: ideation
  frameworks:
    - foundation-sprint
    - click
  timebox_minutes: 75
  roles:
    - facilitator
    - decider
    - pm
    - design
    - engineering
  prerequisites:
    - tool-foundation-sprint-basics
    - tool-foundation-sprint-differentiation
  inputs:
    - basics bundled artifact
    - differentiation bundled artifact
    - approach candidates
  outputs:
    - 3 to 7 one-page approach summaries
    - approach set summary table
  author: product-on-purpose
---

<!-- 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 are emerging organically. The skill caps generation at 7; beyond that the team is generating features, not strategic approaches.

## What This Skill Produces

A single bundled artifact containing:

1. **3 to 7 one-page approach summaries**, each with:
   - Name and label (color, letter, ID)
   - One-sentence "what it is"
   - "Why it's a good idea" rationale (1 short paragraph)
   - Simple doodle or textual visual description
   - How the approach serves the two chosen differentiators
2. **Approach set summary table** comparing all approaches at a glance (label, name, capture mechanism, recall mechanism, primary trade-off).

See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf example.

## Sequence (75 minutes)

### Step 1: Frame the approach space (5 min)

The facilitator restates the differentiation: "We are committing to [differentiator 1] and [differentiator 2]. Approaches that fail either of these are out of scope." This sets the boundary; the team generates inside it, not outside it.

### Step 2: Silent ideation (15-20 min)

Each team member generates 2-4 candidate approaches silently. Cluster duplicates. Surface 8-12 candidates.

### Step 3: Cluster and select 3-7 (15-25 min via Decider call)

The team clusters similar approaches and the Decider narrows to 3-7 candidates that will be one-page-summarized. The 3-minimum is enforced; if the team produces 2 candidates after clustering, push the team back to ideation to generate at least one more.

### Step 4: One-page summarize each approach (25-40 min)

Each team member takes 1-2 approaches and writes the one-page summary. Each summary names:

- **Label**: a color, letter, or short identifier (Yellow, Blue, Approach A, etc.)
- **What it is**: one sentence the customer would understand
- **Why it's a good idea**: short paragraph naming the customer value and the team's ability to deliver
- **Visual**: a simple doodle or textual description of what the customer sees or does
- **How it serves the differentiators**: one or two lines per chosen differentiator

### Step 5: Cross-summary review (5-10 min)

The team reviews the full set, flagging summaries that don't fit the differentiators or that overlap so heavily with another approach that they're duplicates. The Decider approves the set advancing to Magic Lenses.

## Approach Generation Discipline

The skill enforces five rules at decision-point:

1. **Minimum 3, maximum 7.** Fewer than 3 means the team is anchored on one idea; more than 7 means the team is generating features.
2. **Each approach must be a strategic path, not a feature.** "Add a settings screen" is a feature; "make capture the home screen" is a strategic path.
3. **Each approach must serve both chosen differentiators (not just one).** An approach that wins on differentiator 1 but fails differentiator 2 should be either revised or dropped.
4. **Each approach must be visually describable.** If the team can't draw it on a card, the approach is too abstract for the sprint.
5. **No first-idea bias.** The first approach the team thought of should be included only if it survives the differentiation check; many teams find their initial idea is not the strongest after generating alternatives.

## Inference Inputs

| Input | What the skill does with it |
|---|---|
| Basics bundled artifact | Reads target customer to ensure approaches are designed for them, not for an adjacent customer |
| Differentiation bundled artifact | Reads the 2 chosen differentiators and the 2x2 position; flags approaches that miss either differentiator |
| Approach candidates (optional) | If pre-supplied, pre-populates the silent ideation boa

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/product-on-purpose/pm-skills
git -C pm-skills checkout 2abfbb961d31

Works in

1. 2026-10-19
   ✓SAFE B 89 / 100

   first audit · source 2abfbb961d31

Questions about Tool Foundation Sprint Approach Options

• github.com/product-on-purpose/pm-skills/tree/main/skills/tool-fo — the audited source at commit 2abfbb961d31 and every finding aboveObserved · 19 Oct 2026

Spotted something wrong? Report a correction · Methodology