tool-foundation-sprint-brief
Pre-sprint brief that locks scope, the decision the sprint must unlock, team and role assignments, logistics, inputs to bring, and success criteria before Day 1 of a Foundation Sprint. Use after the readiness verdict is Go and before the sprint begins. Produces a one-page artifact the team and Decider sign off on as the contract for the next two days.
npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Foundation Sprint Brief Produce the one-page brief that aligns the team on scope, decision target, participants, logistics, and success criteria before Day 1 begins. A well-built brief prevents Day 1 from opening with re-litigation of why-are-we-here; a missing or vague brief almost guarantees it. Family contract: [`docs/reference/skill-families/foundation-sprint-skills-contract.md`](../../docs/reference/skill-families/foundation-sprint-skills-contract.md). This skill is a member of `foundation-sprint-skills`. ## When to Use - The readiness verdict from `tool-foundation-sprint-readiness` is Go (or Conditional Go with preconditions cleared). - The sprint has dates blocked on calendars and you need the artifact that names what the sprint is for. - The team has prep activities scheduled and you need a written reference for what to bring. - A skeptical exec wants to know "what is the team doing for two days?" and you need an answer that fits on one page. ## When NOT to Use - The sprint has already started. The brief is a prep artifact, not an in-sprint deliverable. If Day 1 is happening, run `tool-found
- When to Use
- When NOT to Use
- What This Skill Produces
- Inference Inputs
- Brief Length Discipline
- Common Pitfalls
- Canonical Sources
- Cross-Skill Usage
- Decider Checkpoint
What does the tool-foundation-sprint-brief skill do?
Pre-sprint brief that locks scope, the decision the sprint must unlock, team and role assignments, logistics, inputs to bring, and success criteria before Day 1 of a Foundation Sprint. Use after the readiness verdict is Go and before the sprint begins. Produces a one-page artifact the team and Decider sign off on as the contract for the next two days.
How do I install it?
Run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.