tool-foundation-sprint-readiness

Installation
SKILL.md

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

Installs
195
GitHub Stars
349
First Seen
May 15, 2026
tool-foundation-sprint-readiness — product-on-purpose/pm-skills