Sprint Brief
mohitagw15856/pm-claude-skills
Generate a structured sprint brief from sprint data and goals.
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.
Apache-2.0Auto-check passed
Install Tool Foundation Sprint Brief
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-foundation-sprint-brief .claude/skills/tool-foundation-sprint-brief && rm -rf skills-srcUse ~/.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/
Install the "tool-foundation-sprint-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-brief into .claude/skills/tool-foundation-sprint-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-foundation-sprint-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tool-foundation-sprint-brief .agents/skills/tool-foundation-sprint-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tool-foundation-sprint-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-brief into .agents/skills/tool-foundation-sprint-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-foundation-sprint-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tool-foundation-sprint-brief .cursor/skills/tool-foundation-sprint-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tool-foundation-sprint-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-brief into .cursor/skills/tool-foundation-sprint-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-foundation-sprint-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/tool-foundation-sprint-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tool-foundation-sprint-brief .gemini/skills/tool-foundation-sprint-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tool-foundation-sprint-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-brief into .gemini/skills/tool-foundation-sprint-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-foundation-sprint-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tool-foundation-sprint-brief .github/skills/tool-foundation-sprint-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tool-foundation-sprint-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-brief into .github/skills/tool-foundation-sprint-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-foundation-sprint-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills tool-foundation-sprint-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tool-foundation-sprint-brief .opencode/skills/tool-foundation-sprint-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tool-foundation-sprint-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-brief into .opencode/skills/tool-foundation-sprint-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-foundation-sprint-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tool-foundation-sprint-brief- GitHub stars
- 716
- Token cost
- ~1.9k tokens
- SKILL.md length
- 916 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 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.
- Works in 6 steps: Initiative statement and stakes: one… → Decision the sprint must unlock: the… → Team roster with role assignments: who… → …
- 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 Foundation Sprint Brief is an agent skill from product-on-purpose/pm-skills. 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.
Its SKILL.md is about 1.9k 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`).
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.
Example prompts
- “/tool-foundation-sprint-brief”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Initiative statement and stakes: one paragraph naming what the team is sprinting on and why a wrong direction would be costly.
- Decision the sprint must unlock: the open strategic question the sprint resolves. Single sentence.
- Team roster with role assignments: who is in the room and what role each person plays per section of the sprint.
- Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
- Existing inputs to bring: the research, customer examples, competitor notes, metrics, and constraints the team should reference during the…
- Readiness reaffirmation: a final check that the Go verdict from tool-foundation-sprint-readiness still holds.
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
No URLs in SKILL.md.
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 Foundation Sprint Brief loads about 1.9k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 916 words of instructions outside code blocks.
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). 916 words, ~1,927 tokens.
Download SKILL.mdSave it as
.claude/skills/tool-foundation-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-foundation-sprint-brief
- description
- 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.
- license
- Apache-2.0
- metadata.classification
- tool
- metadata.version
- 1.0.0
- metadata.updated
- 2026-07-04
- metadata.tool
- foundation-sprint
- metadata.move
- brief
- metadata.category
- coordination
- metadata.frameworks
- foundation-sprint, click
- metadata.timebox_minutes
- 60
- metadata.roles
- facilitator, pm, decider
<!-- 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. This skill is a member of foundation-sprint-skills.
When to Use
- The readiness verdict from
tool-foundation-sprint-readinessis 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-foundation-sprint-basicsinstead. - 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 strategy document. The brief is internal prep, not a stakeholder deliverable. If a stakeholder document is needed, that is a downstream artifact.
- The brief threatens to become a multi-page strategic document. Stop and reframe: the canonical brief is one page.
What This Skill Produces
A single bundled artifact with six sections:
- Initiative statement and stakes: one paragraph naming what the team is sprinting on and why a wrong direction would be costly.
- Decision the sprint must unlock: the open strategic question the sprint resolves. Single sentence.
- Team roster with role assignments: who is in the room and what role each person plays per section of the sprint.
- Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
- Existing inputs to bring: the research, customer examples, competitor notes, metrics, and constraints the team should reference during the sprint.
- Readiness reaffirmation: a final check that the Go verdict from
tool-foundation-sprint-readinessstill holds.
See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for the Brainshelf book-catalog brief.
Inference Inputs
| 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 |
Brief Length Discipline
The brief MUST fit on one page (or one screen). The skill enforces this through structural choices, not raw character counts:
- Initiative Statement: one paragraph, four sentences maximum.
- Decision the sprint must unlock: one sentence.
- Team Roster: table with one row per person.
- Logistics: table.
- Inputs to Bring: bulleted list, five items maximum.
- Readiness Reaffirmation: checklist.
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.
Show full SKILL.md (379 more words)Show less
Common Pitfalls
- Over-engineering the brief. The brief is a prep artifact, not a strategy doc. If it has an executive summary, an appendix, or a "background" section longer than one paragraph, it has drifted.
- Treating the brief as a deliverable to stakeholders. Stakeholders do not read the brief; they read the Founding Hypothesis at the end. The brief is for the team. Sharing it publicly invites pre-sprint debate, which the sprint is supposed to resolve.
- Vague decision target. "We will figure out our strategy" is not a decision. "We will commit to a top bet between [option A] and [option B]" is.
- Logistics drift. "We'll figure out dates" or "we'll meet hybrid sometimes" telegraphs that the team has not actually committed to the sprint. Either dates and format are locked, or the readiness verdict was wrong.
- Skipping readiness reaffirmation. The readiness verdict was a snapshot. If a precondition has slipped or the Decider's availability has changed since readiness, the brief needs to surface that, not paper over it.
Canonical Sources
- Character Capital. "Foundation Sprint guide." Section on pre-sprint preparation and team scoping.
- Knapp, J., and Zeratsky, J. Click: How to Make What People Want. Pre-sprint prep recommendations.
- pm-skills
foundation-meeting-briefprecedent: brief-structure pattern adapted for the strategic context of a Foundation Sprint rather than a meeting.
Cross-Skill Usage
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.
Decider Checkpoint
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.
© 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-foundation-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 Foundation 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tool Foundation Sprint Brief this skillproduct-on-purpose/pm-skills | 716 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Sprint Briefmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Briefalirezarezvani/claude-skills | 28k | — | ~967 | Automated safety check: Pass | MIT | |
| Sprint Planphuryn/pm-skills | 27k | — | ~590 | Automated safety check: Pass | MIT | |
| Sprint Status SnapshotDonchitos/Claude-Code-Game-Studios | 26k | — | ~3k | Automated safety check: Pass | MIT | |
| Sprint Plan BuilderDonchitos/Claude-Code-Game-Studios | 26k | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Brief
alirezarezvani/claude-skills
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
Sprint Plan
phuryn/pm-skills
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.
Sprint Status Snapshot
Donchitos/Claude-Code-Game-Studios
Gives a fast, read-only sprint snapshot with burndown and emerging risks in under 30 lines, plus at most one concrete recommendation.
Sprint Plan Builder
Donchitos/Claude-Code-Game-Studios
Creates or updates a sprint plan from the current milestone, completed work and available capacity, sizing the story count to the project's granularity setting.
Brief
davepoon/buildwithclaude
Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
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.
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.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
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.
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…
Questions about Tool Foundation Sprint Brief
What does Tool Foundation Sprint Brief 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. Tool Foundation Sprint Brief is an agent skill from product-on-purpose/pm-skills. 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.
How do I install Tool Foundation Sprint Brief in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a claude-code`. Or copy the skill folder (skills/tool-foundation-sprint-brief in product-on-purpose/pm-skills) into .claude/skills/tool-foundation-sprint-brief in your project. Claude Code loads it when a task matches its description.
How do I install Tool Foundation Sprint Brief in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-brief -a codex`. Or copy the skill folder (skills/tool-foundation-sprint-brief in product-on-purpose/pm-skills) into .agents/skills/tool-foundation-sprint-brief in your project. Codex loads it when a task matches its description.
Can I use Tool Foundation 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-foundation-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-foundation-sprint-brief, .gemini/skills/tool-foundation-sprint-brief, .github/skills/tool-foundation-sprint-brief and .opencode/skills/tool-foundation-sprint-brief in your project.
What does Tool Foundation Sprint Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Tool Foundation Sprint Brief is instructions for the agent only.
Does Tool Foundation Sprint Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Tool Foundation 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 Foundation Sprint Brief use?
Tool Foundation 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 Foundation Sprint Brief use?
About 1.9k tokens (SKILL.md is roughly 7.7k 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 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Tool Foundation Sprint Brief?
Skills that share tags, products or a category with Tool Foundation Sprint Brief: Sprint Brief (mohitagw15856/pm-claude-skills, 1.4k stars), Brief (alirezarezvani/claude-skills, 28k stars), Sprint Plan (phuryn/pm-skills, 27k stars) and Sprint Status Snapshot (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tool Foundation 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.