Help us improve
Share bugs, ideas, or general feedback.
From pm-skills
Generates a one-page pre-sprint brief for Foundation Sprints, locking scope, decision target, team roles, logistics, and success criteria before Day 1. Use after readiness verdict is Go.
npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:tool-foundation-sprint-briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Produces a two-page design sprint brief that locks challenge, sprint questions, team roles, customer recruiting, prototype medium, interview format, logistics, and success criteria before Monday. Use after readiness verdict is Go.
Generates a structured sprint brief from sprint data and goals, including critical path, risks, and definition of done.
Activate for: sprint, innovation sprint, agile, sprint plan, sprint goal, sprint backlog, user story, acceptance criteria, definition of done, sprint review, sprint retrospective, velocity, iteration, two-week sprint, sprint planning, what to build this sprint, backlog prioritisation, story points, mid-sprint check, sprint close, assumption update, learning sprint. NOT for: idea generation (use idea), assumption mapping (use hypothesis), pilot results analysis (use validate).
Share bugs, ideas, or general feedback.
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. This skill is a member of foundation-sprint-skills.
tool-foundation-sprint-readiness is Go (or Conditional Go with preconditions cleared).tool-foundation-sprint-basics instead.A single bundled artifact with six sections:
tool-foundation-sprint-readiness still holds.See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for the Brainshelf book-catalog brief.
| Input | What the skill does with it |
|---|---|
Readiness verdict and recommendations (from tool-foundation-sprint-readiness) | Pulls the recommended attendees, preconditions, and pre-sprint activities into the brief; flags any precondition that has not been closed |
| Initiative description | Compresses into one paragraph for the Initiative Statement section |
| Team roster | Maps people to the required Foundation Sprint roles (Decider, Facilitator, PM, Design, Engineering, Customer Expert) |
| Logistics constraints | Produces the dates/hours/location/format/tools matrix; flags any constraint that would force the sprint to extend beyond two days |
| (Optional) Skeptical-exec talking points | Tightens the Stakes paragraph to address why-now and why-this concerns |
The brief MUST fit on one page (or one screen). The skill enforces this through structural choices, not raw character counts:
If the brief expands beyond this scope, the sprint is being over-engineered before it starts. The fix is not a longer brief; the fix is a clearer decision target.
foundation-meeting-brief precedent: brief-structure pattern adapted for the strategic context of a Foundation Sprint rather than a meeting.Prerequisites: tool-foundation-sprint-readiness. The brief expects the readiness output as its primary input. When prerequisites is honored, the brief inherits the readiness verdict, attendee recommendations, and pre-sprint activities; the skill then refines and commits them.
If the team has done equivalent prep without running the readiness skill explicitly (e.g., experienced sprint facilitator who knows the readiness criteria), the brief skill can be invoked directly. In that case, the skill body prompts the team to confirm the readiness criteria are met before generating the brief.
Next invocation in the sprint: tool-foundation-sprint-basics on Day 1 morning.
This skill ends with a Decider Checkpoint in references/TEMPLATE.md. The Decider signs off on scope (the decision target), team (the roster and role assignments), success criteria (what makes the sprint successful or not), and the explicit tradeoff that the sprint will force a top bet rather than preserve all directions. Without sign-off, the brief is advisory; with sign-off, it is the contract for the next two days.