tool-foundation-sprint-readiness

Diagnoses team readiness for a Foundation Sprint and produces a Go, Conditional Go, or Wait verdict.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-foundation-sprint-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-foundation-sprint-readiness
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-readiness
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-foundation-sprint-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often commit two days of facilitated work to a Foundation Sprint without checking whether the prerequisites are in place, and most failed sprints were sprints that should never have been run. This Skill runs a 45-minute pre-sprint diagnostic that catches that failure mode before calendar time is committed.

Core Features & Use Cases

  • Eight-criterion readiness check: Evaluates initiative clarity, stakes, existing customer knowledge, Decider availability, team size, collected inputs, path to testing, and tolerance for explicit tradeoffs.
  • Structured verdict output: Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities in a single bundled artifact.
  • Decider Checkpoint: Ends with explicit Decider sign-off so the verdict becomes a commitment rather than advisory input.
  • Use Case: A pre-seed founding team is split between two product directions and considering a Foundation Sprint. Run this diagnostic to confirm the Decider is available, the team has enough customer knowledge, and competitor research gaps are closable before scheduling Day 1.

Quick Start

Assess whether my team is ready to run a Foundation Sprint for our new product initiative and give me a Go, Conditional Go, or Wait verdict with recommended next steps.

Frequently Asked Questions about tool-foundation-sprint-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know if my team is ready for a Foundation Sprint?

Run a readiness diagnostic against eight criteria: named initiative, meaningful stakes, existing customer knowledge, Decider availability, team size of five or fewer, collected inputs, a path to testing, and tolerance for explicit tradeoffs. All eight passing means Go; one or two addressable yellow flags means Conditional Go.

What is the difference between Go, Conditional Go, and Wait verdicts?

Go means all eight readiness criteria pass cleanly. Conditional Go means one or two yellow flags exist that can be closed with documented prep before Day 1. Wait means three or more criteria fail, or any of the first four criteria is a hard fail, requiring prerequisite work first.

When should I not run a Foundation Sprint readiness check?

Skip it when the team has already committed to the sprint and just needs the brief, when deep customer discovery is needed first, when the decision is too small to justify a full sprint, or when no Decider with real authority is available.

Can a Foundation Sprint run without a Decider?

No. A team with no Decider available is not ready, full stop. Appointing a temporary Decider who lacks real authority does not solve this, because the sprint depends on fast strategic calls that produce commitment rather than options.

What happens after a Go verdict in the readiness diagnostic?

The natural next step is setting up sprint logistics with a Foundation Sprint brief. The diagnostic output also includes pre-sprint activities such as compiling competitor research, blocking calendars, and preparing the workspace before Day 1.