New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tool Foundation Sprint Readiness

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

Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first.

Apache-2.0Auto-check passed

Install Tool Foundation Sprint Readiness

skills CLI
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-readiness -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-readiness --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-readiness .claude/skills/tool-foundation-sprint-readiness && 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-readiness
GitHub stars
716
Token cost
~2.1k tokens
SKILL.md length
1,045 words
Files
4 (incl. references)
Skills in repo
68
Repo updated
First seen
Licence
Apache-2.0

At a glance

Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first.

  • Works in 5 steps: Readiness verdict: Go / Conditional Go /… → Diagnosis: what is in place, what is… → Recommended preconditions (when verdict… → …
  • A team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work
  • SKILL.md covers When to Use, When NOT to Use, What This Skill Produces and Inference Inputs, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tool Foundation Sprint Readiness is an agent skill from product-on-purpose/pm-skills. Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.

Its SKILL.md is about 2.1k 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.

When your agent uses it

  • A team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work

Example prompts

  • “/tool-foundation-sprint-readiness”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Readiness verdict: Go / Conditional Go / Wait
  2. Diagnosis: what is in place, what is missing, what is uncertain
  3. Recommended preconditions (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint
  4. Recommended attendee list (when verdict is Go or Conditional Go): the 3-5 people who should be in the room, with role expectations
  5. Pre-sprint activities (when verdict is Go): the prep work to complete in the days before Day 1

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

    Links to these hosts (documentation or services it may open):

    • character.vc

    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 Readiness loads about 2.1k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 1,045 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
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,045 words, ~2,130 tokens.

Download SKILL.mdSave it as .claude/skills/tool-foundation-sprint-readiness/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-readiness
description
Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.
license
Apache-2.0
metadata.classification
tool
metadata.version
1.0.0
metadata.updated
2026-07-04
metadata.tool
foundation-sprint
metadata.move
readiness
metadata.category
coordination
metadata.frameworks
foundation-sprint, click, character-note-and-vote
metadata.timebox_minutes
45
metadata.roles
facilitator, pm, decider
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Foundation Sprint Readiness

Assess whether a Foundation Sprint fits the team's current situation. Most sprints that fail were sprints that should not have been run. A 30-45 minute readiness diagnostic catches that failure mode before two days of facilitated work are spent.

Family contract: docs/reference/skill-families/foundation-sprint-skills-contract.md. This skill is a member of foundation-sprint-skills and conforms to the family frontmatter and Decider Checkpoint requirements.

When to Use

  • A team is considering starting a Foundation Sprint and needs a fast diagnosis before committing two days.
  • A founder or PM has a "should we run a Foundation Sprint?" question and wants structured input rather than a vibes check.
  • An existing sprint commitment is on the calendar and the team wants to validate that prerequisites are in place.
  • Re-running a Foundation Sprint after invalidated assumptions: use to confirm new context is ready.

When NOT to Use

  • The team has already decided to run the sprint and just needs the brief. Use tool-foundation-sprint-brief instead.
  • The team needs deep customer discovery: run customer research or problem framing first; the Foundation Sprint depends on existing customer knowledge.
  • The decision is small and a full Foundation Sprint is overkill. Use a lighter prioritization or decision tool.
  • No Decider is available and one cannot be appointed. Foundation Sprint requires fast strategic calls; without authority it produces options without commitment.

What This Skill Produces

A single bundled artifact with five sections:

  1. Readiness verdict: Go / Conditional Go / Wait
  2. Diagnosis: what is in place, what is missing, what is uncertain
  3. Recommended preconditions (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint
  4. Recommended attendee list (when verdict is Go or Conditional Go): the 3-5 people who should be in the room, with role expectations
  5. Pre-sprint activities (when verdict is Go): the prep work to complete in the days before Day 1

See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for a worked example using the Brainshelf book-catalog thread.

Inference Inputs

The skill runs an inference pass over these inputs to produce the verdict:

InputWhat the skill does with it
Initiative descriptionDetermines whether a Foundation Sprint is the right tool (vs problem framing, customer research, or a Design Sprint)
Team composition draftChecks roster against the Foundation Sprint role requirements; flags missing roles
Decider name and availabilityConfirms Decider can attend both days; flags partial availability as Conditional Go risk
Existing customer/market knowledge level (self-assessed 1-10)Below 5 indicates deep discovery is needed first; 5-7 indicates Conditional Go with research prep; 8+ indicates Go
(Optional) Existing competitor and alternative knowledgeFlags gaps that can be closed by overnight prep
(Optional) Logistics constraintsConfirms two days can actually be cleared

If a load-bearing input is missing or low-confidence, the skill flags it explicitly and proposes how to close the gap before the sprint.

Readiness Criteria (8 Canonical Checks)

The skill evaluates the team against these eight criteria, drawn from Knapp/Zeratsky (Click) and Character Capital's Foundation Sprint guide:

  1. Initiative is named and concrete. The team can name the project, product area, or strategic question.
  2. The stakes are meaningful. A wrong starting direction would be costly.
  3. The team has existing knowledge. Real customer, market, competitor, or domain context to make informed choices.
  4. The Decider is available. Strategic calls can be made during the sprint.
  5. The team is small enough. No more than five core decision participants is preferred.
  6. Inputs are collected. Existing research, customer examples, competitor notes, metrics are ready.
  7. The output has a path to testing. The team can use a Design Sprint, experiment, customer research, or another validation method afterward.
  8. The organization tolerates explicit tradeoffs. Foundation Sprint forces choosing a top bet and a backup, not preserving every possibility.
PatternVerdict
All 8 criteria met cleanlyGo
1-2 criteria are "yellow flags" but addressable in evening prepConditional Go with documented prep
3 or more criteria fail, or any of 1-4 is a hard failWait with recommended prerequisite work

Treat the criteria as load-bearing, not a checklist to game. A team that papers over a real gap with "yes, technically" should get a Conditional Go with the gap surfaced.

Show full SKILL.md (348 more words)Show less

Common Pitfalls

  • Skipping the diagnostic because "we're going to run it anyway." This is the most common cause of failed sprints. The diagnostic costs 45 minutes; the failed sprint costs 16 hours of team time plus opportunity cost.
  • Treating Conditional Go as Go without doing the prep. Conditional Go means "Go after closing these gaps." If the gaps are not closed by Day 1 morning, the sprint enters the failure mode the diagnostic was meant to prevent.
  • Confusing readiness assessment with problem framing. This skill assesses whether to run a Foundation Sprint, not whether the team has the right problem. If the problem is unclear, the verdict is Wait with "do problem framing first" as the precondition.
  • No Decider, no sprint. A team with no Decider available is not ready, full stop. Appointing a "Decider for the day" who lacks real authority does not solve this.
  • Cargo-cult readiness. Reading the criteria and answering yes to all eight without checking does not produce readiness. The skill's value is in the honest diagnosis.

Canonical Sources

  • Knapp, J., and Zeratsky, J. Click: How to Make What People Want. Foundation Sprint readiness guidance.
  • Character Capital. "Foundation Sprint guide." https://www.character.vc/guide/foundation-sprint
  • Design Sprint Academy. "Foundation Sprint readiness criteria for enterprise." Used for the enterprise-context adjustments to canonical readiness.

Cross-Skill Usage

This skill is the entry point of the foundation-sprint-skills family. It has no prerequisites (the metadata.prerequisites field is intentionally empty).

When the verdict is Go, the natural next invocation is tool-foundation-sprint-brief to set up the sprint logistics. When the verdict is Wait, the team typically does prerequisite work (problem framing, customer research) before re-invoking this skill.

tool-note-and-vote may be invoked once during the readiness conversation if the team disagrees on whether a Foundation Sprint is the right tool. In practice, this is rare; the diagnostic is usually conclusive.

Decider Checkpoint

This skill ends with a Decider Checkpoint in references/TEMPLATE.md. The Decider signs off on the verdict (Go / Conditional Go / Wait) and explicitly accepts the diagnosis. Without Decider sign-off, the verdict is advisory; with sign-off, it is the commitment that triggers (or postpones) the sprint.

© 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-readiness 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 Readiness 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 Readiness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tool Foundation Sprint Readiness this skillproduct-on-purpose/pm-skills716—~2.1kAutomated safety check: PassApache-2.0
Sprint Planphuryn/pm-skills27k—~590Automated safety check: PassMIT
Sprint Status SnapshotDonchitos/Claude-Code-Game-Studios26k—~3kAutomated safety check: PassMIT
Sprint Plan BuilderDonchitos/Claude-Code-Game-Studios26k—~4.1kAutomated safety check: PassMIT
Network Bgp Diagnosticsaffaan-m/ECC277k1 repos~1.4kAutomated safety check: PassMIT
Homelab Network Readinessaffaan-m/ECC277k1 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • 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

  • Sprint Status Snapshot

    Donchitos/Claude-Code-Game-Studios

    Gives a fast, read-only sprint snapshot with burndown and emerging risks in under 30 lines, plus at most one concrete recommendation.

    26k GitHub stars~3k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Sprint Plan Builder

    Donchitos/Claude-Code-Game-Studios

    Creates or updates a sprint plan from the current milestone, completed work and available capacity, sizing the story count to the project's granularity setting.

    26k GitHub stars~4.1k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Network Bgp Diagnostics

    affaan-m/ECC

    Diagnostics-only BGP troubleshooting patterns for neighbor state, route exchange, prefix policy, AS path inspection, and safe evidence collection.

    277k GitHub starsUsed in 1 repo~1.4k tokens
    SecurityAuto-check passed

  • Homelab Network Readiness

    affaan-m/ECC

    Readiness checklist for homelab VLAN segmentation, local DNS filtering (Pi-hole, AdGuard Home), and WireGuard-style remote access.

    277k GitHub starsUsed in 1 repo~1.9k tokens
    Backend & APIsAuto-check passed

  • Triage Snmp Diagnostics

    netdata/netdata

    Investigate captured SNMP diagnostics and support bundles, or review diagnostics-tool and evidence-interpretation changes.

    81k GitHub stars~3k tokensUpdated today
    DevOps & CloudAuto-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 Readiness

What does Tool Foundation Sprint Readiness do?

Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Tool Foundation Sprint Readiness is an agent skill from product-on-purpose/pm-skills. Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first.

When should I use Tool Foundation Sprint Readiness?

Tool Foundation Sprint Readiness fits situations like: A team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.

How do I install Tool Foundation Sprint Readiness in Claude Code?

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

How do I install Tool Foundation Sprint Readiness in Codex?

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

Can I use Tool Foundation Sprint Readiness 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-readiness -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-readiness, .gemini/skills/tool-foundation-sprint-readiness, .github/skills/tool-foundation-sprint-readiness and .opencode/skills/tool-foundation-sprint-readiness in your project.

What does Tool Foundation Sprint Readiness need to run?

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

Does Tool Foundation Sprint Readiness access the network?

SKILL.md names 1 domain. As links in the text: character.vc. This is read from the text; nothing was executed.

Is Tool Foundation Sprint Readiness 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 Readiness use?

Tool Foundation Sprint Readiness 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 Readiness use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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.4k tokens, read only when the agent opens those files.

What are the alternatives to Tool Foundation Sprint Readiness?

Skills that share tags, products or a category with Tool Foundation Sprint Readiness: Sprint Plan (phuryn/pm-skills, 27k stars), Sprint Status Snapshot (Donchitos/Claude-Code-Game-Studios, 26k stars), Sprint Plan Builder (Donchitos/Claude-Code-Game-Studios, 26k stars) and Network Bgp Diagnostics (affaan-m/ECC, 277k 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 Readiness?

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.