New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tool Design Sprint Brief

by product-on-purpose in product-on-purpose/pm-skills

Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a…

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Tool Design Sprint Brief

skills CLI
$ npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install product-on-purpose/pm-skills tool-design-sprint-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tool-design-sprint-brief .claude/skills/tool-design-sprint-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tool-design-sprint-brief
GitHub stars
716
Token cost
~2.6k tokens
SKILL.md length
1,227 words
Files
4 (incl. references)
Skills in repo
68
Repo updated
First seen
Licence
Apache-2.0

At a glance

Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a…

  • Works in 9 steps: Challenge statement and why-now: one… → Sprint questions: 2-4 specific questions… → Decider attendance windows: the… → …
  • Tasks that involve Recruiting and HR
  • SKILL.md covers When to Use, When NOT to Use, What This Skill Produces and Inference Inputs, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tool Design Sprint Brief is an agent skill from product-on-purpose/pm-skills. Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint. Use after the readiness verdict is Go and before Monday begins. Produces a two-page artifact the team and Decider sign off on as the contract for the next five days.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `HISTORY.md`, `references/EXAMPLE.md` and `references/TEMPLATE.md`).

It sits in Business, Finance & HR, covering Recruiting and HR. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Recruiting and HR

Example prompts

  • “/tool-design-sprint-brief”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Challenge statement and why-now: one paragraph naming the testable challenge and the urgency that justifies a sprint this week vs. later.
  2. Sprint questions: 2-4 specific questions the Friday testing answers. The highest-risk assumption from any prior Foundation Sprint becomes…
  3. Decider attendance windows: the load-bearing moments (Mon AM, Wed AM, Fri PM at minimum); fully blocked if available.
  4. Team roster with role assignments: who is in the room each day and what role each person plays through the week.
  5. Customer recruiting plan: target profile, source, count, incentive, recruiter owner, recruiting deadline, Friday schedule.
  6. Prototype medium decision: clickable, slideware, service role-play, paper, physical mock, or other; with rationale.
  7. Interview format: live or remote; moderated or unmoderated; recording and consent posture; observer-room setup.
  8. Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
  9. Success criteria: observable outcomes that mark the sprint successful or not.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • character.vc
    • designsprintkit.withgoogle.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tool Design Sprint Brief loads about 2.6k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 1,227 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 1,227 words, ~2,618 tokens.

Download SKILL.mdSave it as .claude/skills/tool-design-sprint-brief/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tool-design-sprint-brief
description
Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint. Use after the readiness verdict is Go and before Monday begins. Produces a two-page artifact the team and Decider sign off on as the contract for the next five days.
license
Apache-2.0
metadata.classification
tool
metadata.version
1.0.0
metadata.updated
2026-07-04
metadata.tool
design-sprint
metadata.move
brief
metadata.category
coordination
metadata.frameworks
design-sprint, sprint
metadata.timebox_minutes
75
metadata.roles
facilitator, pm, decider, researcher
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Design Sprint Brief

Produce the brief that aligns the team on challenge, sprint questions, participants, customer recruiting, prototype medium, interview format, logistics, and success criteria before Monday begins. A well-built brief prevents Monday morning from opening with re-litigation of "what are we testing this week?"; a missing or vague brief almost guarantees it.

Family contract: docs/reference/skill-families/design-sprint-skills-contract.md. This skill is a member of design-sprint-skills.

When to Use

  • The readiness verdict from tool-design-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 customer recruiting active and you need to commit a recruiting plan, honorarium budget, and Friday schedule before recruiting closes.
  • A skeptical exec wants to know "what is the team doing for five days plus customer cost?" and you need an answer that fits on two pages.

When NOT to Use

  • The sprint has already started. The brief is a prep artifact, not an in-sprint deliverable. If Monday is happening, run tool-design-sprint-map-and-target instead.
  • The readiness verdict is Wait. The brief cannot fix an unready team; close the preconditions first, then re-run readiness, then invoke this skill.
  • The team wants a stakeholder strategy document. The brief is internal prep, not an external deliverable. If a stakeholder document is needed, that is a downstream artifact (the Friday scorecard or the next-step memo).
  • Customer recruiting has not started. The brief locks the recruiting plan but cannot replace the recruiter. If no recruiter is named, go back to readiness Wait verdict.

What This Skill Produces

A single bundled artifact with nine sections:

  1. Challenge statement and why-now: one paragraph naming the testable challenge and the urgency that justifies a sprint this week vs. later.
  2. Sprint questions: 2-4 specific questions the Friday testing answers. The highest-risk assumption from any prior Foundation Sprint becomes the lead question.
  3. Decider attendance windows: the load-bearing moments (Mon AM, Wed AM, Fri PM at minimum); fully blocked if available.
  4. Team roster with role assignments: who is in the room each day and what role each person plays through the week.
  5. Customer recruiting plan: target profile, source, count, incentive, recruiter owner, recruiting deadline, Friday schedule.
  6. Prototype medium decision: clickable, slideware, service role-play, paper, physical mock, or other; with rationale.
  7. Interview format: live or remote; moderated or unmoderated; recording and consent posture; observer-room setup.
  8. Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
  9. Success criteria: observable outcomes that mark the sprint successful or not.

See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for the Brainshelf book-catalog brief.

Inference Inputs

InputWhat the skill does with it
Readiness verdict and recommendations (from tool-design-sprint-readiness)Pulls the recommended attendees, customer recruiting plan, pre-sprint activities, and prototype medium proposal; flags any precondition that has not been closed
Challenge descriptionCompresses into the Challenge Statement and derives 2-4 sprint questions
Founding Hypothesis (optional; from a prior Foundation Sprint)The highest-risk assumption from the FS scorecard becomes the lead sprint question; the top bet becomes the design direction; the backup becomes the fallback decision if Friday invalidates
Team rosterMaps people to the required Design Sprint roles (Decider, Facilitator, PM, Design, Engineering, Researcher or Customer Expert); confirms 4-7 person band
Customer recruiting source and planLocks recruiter owner, target profile, source channel, honorarium budget, deadline, and Friday schedule
Format (in-person, remote, hybrid; per Ratified Decision 6)Branches the brief body where format affects authoring: recruiting plan (in-person requires geo-local cohort; remote allows cross-timezone), prototype medium (some media work better in-person; e.g., physical mock), interview format (live vs remote moderated), observer setup (in-room vs Zoom breakout room)
Logistics constraintsProduces the dates/hours/location/tools matrix; flags any constraint that would force the sprint to extend beyond 5 days or split across calendar weeks

Brief Length Discipline

The brief MUST fit on two pages (or two screens). The DS brief is intentionally longer than the FS brief because the customer-recruiting, prototype-medium, and interview-format sections have no FS equivalent and must be committed to before Monday.

  • Challenge Statement: one paragraph, four sentences maximum.
  • Sprint Questions: 2-4 numbered questions, each one sentence.
  • Team Roster: table with one row per person.
  • Customer Recruiting: table.
  • Prototype Medium: one paragraph including rationale.
  • Interview Format: one paragraph.
  • Logistics: table.
  • Success Criteria: 3-5 bulleted outcomes.

If the brief expands beyond two pages, the sprint is being over-engineered before it starts. The fix is not a longer brief; the fix is sharper sprint questions and a clearer prototype medium decision.

Show full SKILL.md (476 more words)Show less

Common Pitfalls

  • Vague sprint questions. "Will users like it?" is not a sprint question. "Will 25+/year readers complete sub-3-second camera capture without abandoning?" is. Sprint questions must be answerable from Friday's 5-customer interviews.
  • Recruiting plan that does not match target customer. Recruiting from a panel that skews younger or different demographics than the named target produces Friday data that does not test the actual assumption. Cross-check recruiting source against the readiness customer profile.
  • Skipping prototype medium decision. Leaving prototype medium to Thursday morning forces the team into ad-hoc choice and risks the prototype not being testable Friday. Lock it in the brief; if needed, change it after Wednesday's storyboard but commit a default upfront.
  • Treating the brief as a stakeholder deliverable. Stakeholders read the Friday scorecard and the Decider's next-step memo, not the brief. Sharing the brief publicly invites pre-sprint debate, which the sprint is supposed to resolve.
  • Logistics drift. "We'll figure out remote vs in-person sometimes" telegraphs that the team has not committed. Either format is locked, or the readiness verdict was wrong.
  • No interview format decision. Friday interview moderator, observation-room setup, and recording/consent posture should be in the brief. Forgetting these is the most common cause of Friday running long.

Canonical Sources

  • Knapp, J., Zeratsky, J., and Kowitz, B. Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon and Schuster, 2016. Chapter 3 "Set the Stage" on sprint brief composition.
  • Character Capital. "Design Sprint pre-sprint guide." https://www.character.vc
  • Google Design Sprint Kit. "Sprint brief template." https://designsprintkit.withgoogle.com/
  • AJ and Smart "Remote Design Sprint" template. Adapted for the remote and hybrid format sections.

Cross-Skill Usage

Prerequisites: tool-design-sprint-readiness. The brief expects the readiness output as its primary input. When prerequisites is honored, the brief inherits the readiness verdict, customer recruiting plan draft, attendee recommendations, and pre-sprint activities; the skill then refines and locks 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.

A team coming from a Foundation Sprint should bring the Founding Hypothesis and assumption scorecard as inputs. The brief's Sprint Questions section pulls the highest-risk assumption verbatim as the lead question. No bridge skill is required; the narrative handoff is documented in _workflows/foundation-to-design.md.

Next invocation in the sprint: tool-design-sprint-map-and-target on Monday morning.

Decider Checkpoint

This skill ends with a Decider Checkpoint in references/TEMPLATE.md. The Decider signs off on scope (the challenge and sprint questions), team (the roster and attendance windows), recruiting plan (target profile, source, honorarium budget), prototype medium, interview format, and the explicit success criteria. Without sign-off, the brief is advisory; with sign-off, it is the contract for the next five days and the authorization for customer-recruiting spend.

© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/tool-design-sprint-brief of product-on-purpose/pm-skills.

  • SKILL.md
  • HISTORY.md
  • references/EXAMPLE.md
  • references/TEMPLATE.md

Open the folder on GitHubat commit 1cef1a9

Compare with similar skills

Tool Design Sprint Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tool Design Sprint Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tool Design Sprint Brief this skillproduct-on-purpose/pm-skills716—~2.6kAutomated safety check: PassApache-2.0
Get Jobagentenatalie/get-job.skill632—~1.7kAutomated safety check: PassCC-BY-NC-ND-4.0
Resume Reviewerweeelin98/ResumeDom173—~2.4kAutomated safety check: PassNone
Build Resume Portfolio Sitetao943/build-resume-portfolio-site195—~5.8kAutomated safety check: PassNone
Cyber Resume Reviewermubix/cyber-resume-reviewer-skill184—~2.9kAutomated safety check: PassMIT
Repo To Resume TailorSsabby1/repo-to-resume-tailor127—~1.8kAutomated safety check: PassMIT

Similar skills

  • Get Job

    agentenatalie/get-job.skill

    实习.skill / get-job.skill：从岗位调研、简历改写到分轮次面试准备的全流程求职 skill。适合找工作、投实习、校招、秋招、春招、暑期实习、社招、跳槽、转行、跨专业求职、留学生求职，以及产品经理、运营、市场、咨询、AI 产品、AI Coding、数据分析、技术岗等目标岗位准备。

    632 GitHub stars~1.7k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

  • Resume Reviewer

    weeelin98/ResumeDom

    Build, assess, review, and tailor evidence-backed US-market technology resumes for computer-science interns and new graduates.

    173 GitHub stars~2.4k tokensUpdated 15 days ago
    Business, Finance & HRAuto-check passed

  • Build Resume Portfolio Site

    tao943/build-resume-portfolio-site

    A skill your agent uses when turning resume materials and an optional job description into verified, approved content and a runnable React + Vite resume or portfolio site, or when redesigning an…

    195 GitHub stars~5.8k tokensUpdated 10 days ago
    Business, Finance & HRAuto-check passed

  • Cyber Resume Reviewer

    mubix/cyber-resume-reviewer-skill

    Review, tailor, score, or rewrite IT and cybersecurity resumes.

    184 GitHub stars~2.9k tokensUpdated 20 days ago
    Business, Finance & HRAuto-check passed

  • Repo To Resume Tailor

    Ssabby1/repo-to-resume-tailor

    Analyze a full code repository and generate one resume-ready project description grounded in repository evidence.

    127 GitHub stars~1.8k tokensUpdated 6 mo ago
    Business, Finance & HRAuto-check passed

  • GitHub Project Contributor Finder API Skill

    browser-act/skills

    This skill helps users extract GitHub repository project details and contributor contact information using keywords, stars, and update dates.

    6.1k GitHub starsUsed in 1 repo~1.9k tokens
    Business, Finance & HRAuto-check passed

More from product-on-purpose/pm-skills

All 68 skills in this repo

  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    716 GitHub stars~966 tokensUpdated 3 days ago
    Auto-check passed

  • Define Jtbd Canvas

    product-on-purpose/pm-skills

    Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.

    716 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    716 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Define Problem Statement

    product-on-purpose/pm-skills

    Creates a clear problem framing document with user impact, business context, and success criteria.

    716 GitHub stars~932 tokensUpdated 3 days ago
    Auto-check passed

  • Deliver Acceptance Criteria

    product-on-purpose/pm-skills

    Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.

    716 GitHub stars~1k tokensUpdated 3 days ago
    Auto-check passed

  • Deliver Launch Checklist

    product-on-purpose/pm-skills

    Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…

    716 GitHub stars~970 tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Tool Design Sprint Brief

What does Tool Design Sprint Brief do?

Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a…. Tool Design Sprint Brief is an agent skill from product-on-purpose/pm-skills. Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint.

When should I use Tool Design Sprint Brief?

Tool Design Sprint Brief fits situations like: tasks that involve Recruiting and HR.

How do I install Tool Design Sprint Brief in Claude Code?

Run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-brief -a claude-code`. Or copy the skill folder (skills/tool-design-sprint-brief in product-on-purpose/pm-skills) into .claude/skills/tool-design-sprint-brief in your project. Claude Code loads it when a task matches its description.

How do I install Tool Design Sprint Brief in Codex?

Run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-brief -a codex`. Or copy the skill folder (skills/tool-design-sprint-brief in product-on-purpose/pm-skills) into .agents/skills/tool-design-sprint-brief in your project. Codex loads it when a task matches its description.

Can I use Tool Design Sprint Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tool-design-sprint-brief, .gemini/skills/tool-design-sprint-brief, .github/skills/tool-design-sprint-brief and .opencode/skills/tool-design-sprint-brief in your project.

What does Tool Design Sprint Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Tool Design Sprint Brief is instructions for the agent only.

Does Tool Design Sprint Brief access the network?

SKILL.md names 2 domains. As links in the text: character.vc and designsprintkit.withgoogle.com. This is read from the text; nothing was executed.

Is Tool Design Sprint Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tool Design Sprint Brief use?

Tool Design Sprint Brief is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tool Design Sprint Brief use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Tool Design Sprint Brief?

Skills that share tags, products or a category with Tool Design Sprint Brief: Get Job (agentenatalie/get-job.skill, 632 stars), Resume Reviewer (weeelin98/ResumeDom, 173 stars), Build Resume Portfolio Site (tao943/build-resume-portfolio-site, 195 stars) and Cyber Resume Reviewer (mubix/cyber-resume-reviewer-skill, 184 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tool Design Sprint Brief?

product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.

Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.