<!-- 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: site/src/content/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: