tool-foundation-sprint-brief

Generates a one-page pre-sprint brief locking scope, decision target, roster, and logistics for a Foundation Sprint.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams entering a two-day Foundation Sprint often start Day 1 re-litigating why they are in the room because scope, the decision to unlock, roles, and logistics were never committed to writing. This Skill produces a signed one-page brief that serves as the contract for the sprint before Day 1 begins.

Core Features & Use Cases

  • Six-section brief generation: Produces the initiative statement and stakes, the single-sentence decision the sprint must unlock, a team roster with role assignments, a logistics plan, a list of existing inputs to bring, and a readiness reaffirmation checklist.
  • Readiness integration: Consumes the Go verdict, attendee recommendations, and preconditions from the tool-foundation-sprint-readiness skill and flags any precondition that remains open.
  • Decider Checkpoint: Ends with a sign-off block where the Decider confirms scope, team, success criteria, and the tradeoff that one direction becomes the top bet.
  • Use Case: After a Go readiness verdict for a product initiative, a facilitator invokes this Skill with the initiative description, team roster, and logistics constraints to produce the one-page brief the Decider signs before the sprint starts.

Quick Start

Use the foundation sprint brief skill to draft a one-page pre-sprint brief for our two-day sprint, covering the decision we must unlock, the team roster, logistics, inputs to bring, and the Decider sign-off.

Frequently Asked Questions about tool-foundation-sprint-brief

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

FAQPage Schema
How do I prepare a brief before a Foundation Sprint?

Run this skill after a Go readiness verdict to generate a one-page brief with six sections: initiative statement, the decision to unlock, team roster, logistics, inputs to bring, and readiness reaffirmation. The Decider signs it before Day 1.

What should a Foundation Sprint brief include?

The brief includes an initiative statement with stakes, a single-sentence decision the sprint must unlock, a roster mapping people to sprint roles, a logistics table, up to five existing inputs to bring, success criteria, and a Decider Checkpoint sign-off.

When should I not create a sprint brief?

Skip the brief if the sprint has already started, if the readiness verdict is Wait, or if the document is drifting into a multi-page strategy artifact. The brief is a one-page internal prep contract, not a stakeholder deliverable.

Does the sprint brief require the readiness skill first?

The brief expects the readiness verdict as its primary input, inheriting attendee recommendations and preconditions. Experienced facilitators can invoke it directly, but the skill then prompts confirmation that readiness criteria are met.

Why does a sprint brief need Decider sign-off?

Without sign-off the brief is only advisory. The Decider confirms scope, roster, success criteria, and the tradeoff that one direction becomes the top bet, making the brief the binding contract for the two sprint days.