Agent skill

Tool Foundation Sprint Magic Lenses

by product-on-purpose in product-on-purpose/pm-skills

Day 2 afternoon move of a Foundation Sprint. An agent skill from product-on-purpose/pm-skills.

Apache-2.0Auto-check passed

Install Tool Foundation Sprint Magic Lenses

skills CLI
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-magic-lenses -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-magic-lenses --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tool-foundation-sprint-magic-lenses .claude/skills/tool-foundation-sprint-magic-lenses && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tool-foundation-sprint-magic-lenses
GitHub stars
716
Token cost
~2.3k tokens
SKILL.md length
1,174 words
Files
4 (incl. references)
Skills in repo
68
Repo updated
First seen
Licence
Apache-2.0

At a glance

Day 2 afternoon move of a Foundation Sprint. An agent skill from product-on-purpose/pm-skills.

  • Works in 6 steps: Frame the lenses (5 min) → Score each approach per lens (40-60 min) → Pattern review (15-25 min) → …
  • SKILL.md covers When to Use, When NOT to Use, What This Skill Produces and The Five Canonical Lenses, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tool Foundation Sprint Magic Lenses is an agent skill from product-on-purpose/pm-skills. Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and contradictions, and produce a top bet plus a backup plan. Use after Approach Options is signed. Lens scoring is a sense-making tool, not mathematical truth; arbitrary precision is a smell.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `HISTORY.md`, `references/EXAMPLE.md` and `references/TEMPLATE.md`).

The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.

Example prompts

  • “/tool-foundation-sprint-magic-lenses”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Frame the lenses (5 min)
  2. Score each approach per lens (40-60 min)
  3. Pattern review (15-25 min)
  4. Decider supervote on top bet (10-15 min)
  5. Decider names backup plan (5-10 min)
  6. Decision rationale (5-10 min)

What it can do on your machine

Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tool Foundation Sprint Magic Lenses loads about 2.3k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 1,174 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 1,174 words, ~2,289 tokens.

Download SKILL.mdSave it as .claude/skills/tool-foundation-sprint-magic-lenses/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tool-foundation-sprint-magic-lenses
description
Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and contradictions, and produce a top bet plus a backup plan. Use after Approach Options is signed. Lens scoring is a sense-making tool, not mathematical truth; arbitrary precision is a smell.
license
Apache-2.0
metadata.classification
tool
metadata.version
1.0.0
metadata.updated
2026-07-04
metadata.tool
foundation-sprint
metadata.move
magic-lenses
metadata.category
validation
metadata.frameworks
foundation-sprint, click, character-note-and-vote
metadata.timebox_minutes
105
metadata.roles
facilitator, decider, pm
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Foundation Sprint Magic Lenses

Day 2 afternoon of a Foundation Sprint. The team evaluates each candidate approach from multiple perspectives, surfaces contradictions, and produces a top bet plus a backup plan. The Decider names both; without an explicit backup, invalidation of the top bet sends the team back to ambiguous debate.

Family contract: docs/reference/skill-families/foundation-sprint-skills-contract.md. This skill is a member of foundation-sprint-skills.

When to Use

  • Day 2 afternoon of a Foundation Sprint.
  • Approach Options is signed; the team has 3-7 candidate approaches advancing.
  • The team has at least 1 team-specific custom lens prepared (per ratified spec decision; classic lenses alone are insufficient).

When NOT to Use

  • Approach Options is unresolved or under-numbered (fewer than 3). Force a third option through the approach-options skill first.
  • The team has pre-committed to a top bet. Magic Lenses is a sense-making exercise; if the decision is already made, the time is better spent on Founding Hypothesis.
  • The team is exhausted and cannot evaluate clearly. Postpone to Day 2 morning of a follow-up sprint rather than rush.

What This Skill Produces

A single bundled artifact with six sections:

  1. Classic lens charts: customer, pragmatic, growth, money lenses each as a 2x2 plot or qualitative position of every approach.
  2. Custom lens charts: at least 1 team-specific lens (defensibility, mission fit, founder excitement, learning rate, etc.).
  3. Pattern review: consistent winners across lenses, contradictions, biggest trade-off the team is making.
  4. Top bet: the Decider's chosen approach with rationale.
  5. Backup plan: the runner-up approach the team falls back to if the top bet invalidates.
  6. Decision rationale: one paragraph explaining why the top bet over the backup.

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

The Five Canonical Lenses

LensWhat it asksWhy it matters
CustomerWhich approach do target customers immediately understand and want?If customers don't get it, nothing else matters
PragmaticWhich approach can the team ship at quality in [build window]?Beautiful approaches the team can't ship are not real options
GrowthWhich approach gives the team a story strong enough to acquire users without paid channels?Friction at the door tells you about word-of-mouth potential
MoneyWhich approach has the cleanest path to a paying customer?Strategic clarity must include the revenue path
Custom (1+ required)Team-specific lens that captures what would otherwise be missedEach team has a unique constraint or opportunity worth a dedicated view

Custom lens examples: defensibility against a specific competitor, founder excitement, mission fit, learning rate, regulatory risk, partner alignment, hiring leverage.

Sequence (105 minutes)

Step 1: Frame the lenses (5 min)

Facilitator restates the 4 classic lenses and confirms the 1 or more custom lenses the team prepared. If no custom lens is prepared, this skill prompts the team to generate one before proceeding (per ratified spec decision).

Step 2: Score each approach per lens (40-60 min)

For each lens, plot each approach on a 2x2 of (high/low value on that lens) by (high/low feasibility for that lens). Use dot positions rather than numeric scores; arbitrary precision (3.7 vs 3.8) is a smell that the team has confused sense-making with math.

The team discusses each lens briefly before plotting. Decider does not vote in this step; the Decider supervotes at the end.

Step 3: Pattern review (15-25 min)

After all lenses are plotted, the team identifies:

  • Consistent winners: approaches that score in the top half of 3 or more lenses.
  • Consistent losers: approaches that score in the bottom half of 3 or more lenses. These drop out.
  • Contradictions: approaches that win one lens hard but lose another. These surface the trade-offs the Decider must make.
  • Biggest trade-off: name it explicitly. "Boring-and-shippable vs risky-and-distinctive." "Mass-market vs niche-defensible." Naming the trade-off prevents the Decider from picking by vibes.
Step 4: Decider supervote on top bet (10-15 min)

The Decider names the top bet. The chosen approach should be:

  • A consistent winner OR a contradictory approach the Decider explicitly chooses to take the bet on.
  • Defensible in language ("we are betting [trade-off] because [reason]").
  • Aligned with the Mini Manifesto from Day 1.
Show full SKILL.md (495 more words)Show less
Step 5: Decider names backup plan (5-10 min)

The Decider names the backup. The backup is NOT a second-place approach to soothe whoever advocated for it; it is the approach the team will pivot to if the top bet fails validation. The backup MUST be distinct from the top bet in strategic direction.

If the top bet and backup are too similar, the Decider has not named a real backup. The skill prompts for a more distinct alternative.

Step 6: Decision rationale (5-10 min)

The Decider authors one paragraph explaining why this top bet over this backup. The rationale will become the spine of the Founding Hypothesis's "why we believe this" section.

Common Pitfalls

  • Treating lens scoring as mathematical truth. Lenses are sense-making tools; if the team argues about whether an approach scores 3.7 or 3.8 on a lens, the team has lost the plot.
  • Skipping the custom lens. The 4 classic lenses are generic by design. The custom lens is where the team's specific situation shows up; skipping it produces a generic top bet.
  • Falling in love with the top bet. Confidence after Magic Lenses should be calibrated, not high. The next skill, Founding Hypothesis, asks "what could prove us wrong"; the team that has fallen in love with the top bet cannot answer that question honestly.
  • Skipping the backup plan. Without an explicit backup, invalidation sends the team back to ambiguous debate. The backup forces the team to acknowledge that the top bet might fail.
  • Backup that is too similar to top bet. "Approach Yellow with one feature added" is not a backup; it's an iteration. Backup must be a different strategic direction.
  • Decider names top bet by enthusiasm, not by analysis. The pattern review exists to give the Decider a structured basis for the call. If the Decider picks before the pattern review, the skill provided no value.

Decider Role

The Decider's job during Magic Lenses:

  1. Listen during lens scoring without telegraphing preferences.
  2. Engage during pattern review to surface the trade-off explicitly.
  3. Supervote the top bet with rationale.
  4. Name the backup plan as a distinct strategic direction.
  5. Author the one-paragraph decision rationale.

Canonical Sources

  • Character Capital. "Foundation Sprint guide." Magic Lenses section and lens definitions.
  • Knapp, J., and Zeratsky, J. Click. Day 2 afternoon sequence.
  • Knapp, J., and Zeratsky, J. "Introducing the Foundation Sprint." Lenny's Newsletter. Magic Lenses section.

Cross-Skill Usage

Prerequisites: tool-foundation-sprint-approach-options. The approach set is the load-bearing input.

The skill invokes tool-note-and-vote at least once (for the top bet supervote when scoring is ambiguous). Additional invocations may happen for the custom lens definition if the team has not pre-prepared one.

Next invocation: tool-foundation-sprint-founding-hypothesis at Day 2 end. The top bet, the backup, and the decision rationale flow directly into the Founding Hypothesis template.

Decider Checkpoint

This skill ends with a Decider Checkpoint in references/TEMPLATE.md. The Decider signs off on the top bet, the backup, and the decision rationale. Without sign-off, Founding Hypothesis cannot start cleanly.

© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/tool-foundation-sprint-magic-lenses of product-on-purpose/pm-skills.

  • SKILL.md
  • HISTORY.md
  • references/EXAMPLE.md
  • references/TEMPLATE.md

Open the folder on GitHubat commit 1cef1a9

Compare with similar skills

Tool Foundation Sprint Magic Lenses next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tool Foundation Sprint Magic Lenses compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tool Foundation Sprint Magic Lenses this skillproduct-on-purpose/pm-skills716—~2.3kAutomated safety check: PassApache-2.0
Arize Evaluatorgithub/awesome-copilot40k1 repos~8.1kAutomated safety check: NotesMIT
LLM Evaluationdavila7/claude-code-templates33k12 repos~3.5kAutomated safety check: PassMIT
Agent Evaluationsickn33/agentic-awesome-skills47k1 repos~2kAutomated safety check: PassMIT
Sprint Planphuryn/pm-skills27k—~590Automated safety check: PassMIT
EvaluatorsArize-ai/phoenix12k—~1.7kAutomated safety check: PassCustom licence

Similar skills

  • Arize Evaluator

    github/awesome-copilot

    Official

    Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…

    40k GitHub starsUsed in 1 repo~8.1k tokens
    AI & LLM EngineeringAuto-check: notes
  • LLM Evaluation

    davila7/claude-code-templates

    Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.

    33k GitHub starsUsed in 12 repos~3.5k tokens
    AI & LLM EngineeringAuto-check passed
  • Agent Evaluation

    sickn33/agentic-awesome-skills

    Evaluate agent behavior with versioned cases and explicit verifiers.

    47k GitHub starsUsed in 1 repo~2k tokens
    Agent WorkflowsAuto-check passed
  • Sprint Plan

    phuryn/pm-skills

    Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.

    27k GitHub stars~590 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Evaluators

    Arize-ai/phoenix

    Author or refine a Phoenix evaluator — code or LLM-as-a-judge — that scores a run's output.

    12k GitHub stars~1.7k tokensUpdated yesterday
    EducationAuto-check passed
  • Agent Evaluation Reporting

    sickn33/agentic-awesome-skills

    A skill your agent uses when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from product-on-purpose/pm-skills

All 68 skills in this repo
  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    716 GitHub stars~966 tokensUpdated 3 days ago
    Auto-check passed
  • Define Jtbd Canvas

    product-on-purpose/pm-skills

    Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.

    716 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed
  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    716 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed
  • Define Problem Statement

    product-on-purpose/pm-skills

    Creates a clear problem framing document with user impact, business context, and success criteria.

    716 GitHub stars~932 tokensUpdated 3 days ago
    Auto-check passed
  • Deliver Acceptance Criteria

    product-on-purpose/pm-skills

    Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.

    716 GitHub stars~1k tokensUpdated 3 days ago
    Auto-check passed
  • Deliver Launch Checklist

    product-on-purpose/pm-skills

    Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…

    716 GitHub stars~970 tokensUpdated 3 days ago
    Auto-check passed

Questions about Tool Foundation Sprint Magic Lenses

What does Tool Foundation Sprint Magic Lenses do?

Day 2 afternoon move of a Foundation Sprint. An agent skill from product-on-purpose/pm-skills. Tool Foundation Sprint Magic Lenses is an agent skill from product-on-purpose/pm-skills. Day 2 afternoon move of a Foundation Sprint.

How do I install Tool Foundation Sprint Magic Lenses in Claude Code?

Run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-magic-lenses -a claude-code`. Or copy the skill folder (skills/tool-foundation-sprint-magic-lenses in product-on-purpose/pm-skills) into .claude/skills/tool-foundation-sprint-magic-lenses in your project. Claude Code loads it when a task matches its description.

How do I install Tool Foundation Sprint Magic Lenses in Codex?

Run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-magic-lenses -a codex`. Or copy the skill folder (skills/tool-foundation-sprint-magic-lenses in product-on-purpose/pm-skills) into .agents/skills/tool-foundation-sprint-magic-lenses in your project. Codex loads it when a task matches its description.

Can I use Tool Foundation Sprint Magic Lenses in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-magic-lenses -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tool-foundation-sprint-magic-lenses, .gemini/skills/tool-foundation-sprint-magic-lenses, .github/skills/tool-foundation-sprint-magic-lenses and .opencode/skills/tool-foundation-sprint-magic-lenses in your project.

What does Tool Foundation Sprint Magic Lenses need to run?

SKILL.md names no scripts, command-line tools or credentials: Tool Foundation Sprint Magic Lenses is instructions for the agent only.

Does Tool Foundation Sprint Magic Lenses access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tool Foundation Sprint Magic Lenses safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tool Foundation Sprint Magic Lenses use?

Tool Foundation Sprint Magic Lenses is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tool Foundation Sprint Magic Lenses use?

About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Tool Foundation Sprint Magic Lenses?

Skills that share tags, products or a category with Tool Foundation Sprint Magic Lenses: Arize Evaluator (github/awesome-copilot, 40k stars), LLM Evaluation (davila7/claude-code-templates, 33k stars), Agent Evaluation (sickn33/agentic-awesome-skills, 47k stars) and Sprint Plan (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tool Foundation Sprint Magic Lenses?

product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.

Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.