tool-design-sprint-brief

Generates a two-page pre-sprint brief locking challenge, team, recruiting, and success criteria for a Design Sprint.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams entering a five-day Design Sprint often start Monday re-litigating what they are testing, who attends, and how customers will be recruited. This Skill produces a signed two-page brief that locks the challenge, sprint questions, roles, recruiting plan, prototype medium, interview format, logistics, and success criteria before the sprint begins.

Core Features & Use Cases

  • Nine-Section Brief Generation: Produces challenge statement, sprint questions, Decider attendance windows, team roster, customer recruiting plan, prototype medium decision, interview format, logistics, and success criteria in one artifact.
  • Readiness Integration: Consumes the Go verdict and recommendations from the design-sprint-readiness step, and pulls the highest-risk assumption from a prior Foundation Sprint as the lead sprint question.
  • Decider Checkpoint: Ends with a sign-off checklist that turns the brief into the contract for the next five days and authorizes customer-recruiting spend.
  • Use Case: A product team with a Go readiness verdict needs to commit a recruiting budget, lock a Figma prototype medium, and get Decider sign-off before Monday; the Skill outputs the complete brief using the provided template and a worked example.

Quick Start

Use the design sprint brief skill to draft a pre-sprint brief for our upcoming five-day sprint based on our readiness verdict and team roster.

Frequently Asked Questions about tool-design-sprint-brief

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

FAQPage Schema
How do I write a design sprint brief before Monday?

Gather the readiness verdict, challenge description, team roster, recruiting plan, format decision, and logistics constraints, then fill the nine-section template covering challenge, sprint questions, roster, recruiting, prototype medium, interview format, logistics, and success criteria. Keep it to two pages and get Decider sign-off before the sprint starts.

What should a design sprint brief include?

A design sprint brief includes a challenge statement with why-now, 2-4 sprint questions, Decider attendance windows, a team roster with role assignments, a customer recruiting plan, a prototype medium decision, an interview format, a logistics plan, and explicit success criteria.

When should I not create a design sprint brief?

Skip the brief if the sprint has already started, if the readiness verdict is Wait, or if customer recruiting has not begun. The brief is a pre-sprint contract, not an in-sprint deliverable or a stakeholder communication document.

How many sprint questions should a design sprint brief have?

A brief should contain 2-4 sprint questions, each one sentence and answerable from the five Friday customer interviews. If a Foundation Sprint preceded the sprint, the highest-risk assumption from its scorecard becomes the lead question.

Who signs off on a design sprint brief?

The Decider signs off on the brief before Monday begins, confirming scope, team roster, recruiting plan and budget, prototype medium, interview format, and success criteria. Without sign-off the brief is advisory; with sign-off it becomes the contract for the five days.