Sprint Plan
phuryn/pm-skills
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch).
Apache-2.0Auto-check passed
Install Tool Design Sprint Sketch
$ npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-sketch -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills tool-design-sprint-sketch --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-design-sprint-sketch .claude/skills/tool-design-sprint-sketch && 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-design-sprint-sketch" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-sketch into .claude/skills/tool-design-sprint-sketch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-design-sprint-sketch", 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-design-sprint-sketchType 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-design-sprint-sketch -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills tool-design-sprint-sketch --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-design-sprint-sketch .agents/skills/tool-design-sprint-sketch && 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-design-sprint-sketch" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-sketch into .agents/skills/tool-design-sprint-sketch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-design-sprint-sketch", 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-design-sprint-sketch -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills tool-design-sprint-sketch --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-design-sprint-sketch .cursor/skills/tool-design-sprint-sketch && 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-design-sprint-sketch" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-sketch into .cursor/skills/tool-design-sprint-sketch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-design-sprint-sketch", 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-design-sprint-sketch--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-design-sprint-sketch -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills tool-design-sprint-sketch --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-design-sprint-sketch .gemini/skills/tool-design-sprint-sketch && 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-design-sprint-sketch" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-sketch into .gemini/skills/tool-design-sprint-sketch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-design-sprint-sketch", 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-design-sprint-sketchInstalls 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-design-sprint-sketch -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-design-sprint-sketch .github/skills/tool-design-sprint-sketch && 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-design-sprint-sketch" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-sketch into .github/skills/tool-design-sprint-sketch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-design-sprint-sketch", 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-design-sprint-sketch -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-design-sprint-sketch --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-design-sprint-sketch .opencode/skills/tool-design-sprint-sketch && 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-design-sprint-sketch" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-sketch into .opencode/skills/tool-design-sprint-sketch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tool-design-sprint-sketch", 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-design-sprint-sketch- GitHub stars
- 716
- Token cost
- ~2.1k tokens
- SKILL.md length
- 945 words
- Files
- 4 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch).
- Works in 4 steps: Lightning demo board: each team member… → Sketch assignment plan: divide (each… → Four-step sketches from each team… → …
- SKILL.md covers When to Use, When NOT to Use, What This Skill Produces and Tuesday Time Structure, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Tool Design Sprint Sketch is an agent skill from product-on-purpose/pm-skills. Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themselves. Use Tuesday morning after Monday's target moment is locked. Output is the lightning demo board, sketch assignments, and the cohort of independent sketches that become Wednesday's heat-map material.
Its SKILL.md is about 2.1k 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-design-sprint-sketch”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Lightning demo board: each team member presents 3 demos (3 minutes each); the Facilitator extracts the reusable pattern from each demo…
- Sketch assignment plan: divide (each person sketches a different part of the target moment) or swarm (everyone sketches the same target)…
- Four-step sketches from each team member: Notes (20 min reviewing Monday output + lightning demos), Ideas (20 min rough doodles), Crazy 8s…
- Recruiting tracker update: Riley (or the recruiter) confirms Friday slots; surfaces any cancellations and triggers buffer-slot activation…
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):
gv.comcharacter.vcdesignsprintkit.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 Sketch loads about 2.1k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 945 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). 945 words, ~2,114 tokens.
Download SKILL.mdSave it as
.claude/skills/tool-design-sprint-sketch/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-sketch
- description
- Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themselves. Use Tuesday morning after Monday's target moment is locked. Output is the lightning demo board, sketch assignments, and the cohort of independent sketches that become Wednesday's heat-map material.
- license
- Apache-2.0
- metadata.classification
- tool
- metadata.version
- 1.0.0
- metadata.updated
- 2026-07-04
- metadata.tool
- design-sprint
- metadata.move
- sketch
- metadata.category
- discovery
- metadata.frameworks
- design-sprint, sprint
- metadata.timebox_minutes
- 180
- metadata.roles
- facilitator, decider, pm, design, engineering, researcher, customer-expert
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->Design Sprint Sketch (Tuesday)
Structure Tuesday's solo-but-together work. Each team member, working independently and silently, produces lightning demos in the morning and a four-step solution sketch in the afternoon. The skill structures the activity; the humans produce the sketches. Wednesday's heat-map orientation depends on having a cohort of independent sketches that did NOT contaminate each other through group brainstorming.
Family contract: docs/reference/skill-families/design-sprint-skills-contract.md. This skill is a member of design-sprint-skills.
When to Use
- It is Day 2 of the Design Sprint and Monday's Map and Target artifact is signed off.
- Each team member brings at least 3 lightning demo sources (existing products, references, analogies that bear on the challenge).
- The team has accepted the silent-independent-sketching constraint and will NOT lapse into group brainstorming.
- Sketches are due Tuesday end-of-day for Wednesday morning heat-map.
When NOT to Use
- Monday is not closed. Return to
tool-design-sprint-map-and-target. - The team's instinct is to brainstorm as a group. Sprint method explicitly avoids this; if the team will not commit to independent work, the sprint will not produce diverse sketches and the heat-map becomes a popularity contest.
- The sketch step is being treated as the prototype. Sketches are concept exploration on paper or Figma frames, not Thursday's working prototype.
- Sketches are due Tuesday morning. Tuesday is the full day; rushing to lunch produces sketches the team cannot read Wednesday.
What This Skill Produces
A single bundled artifact with four sections:
- Lightning demo board: each team member presents 3 demos (3 minutes each); the Facilitator extracts the reusable pattern from each demo into a one-line note. Result is a board with 12-21 patterns (4-7 team members x 3 demos).
- Sketch assignment plan: divide (each person sketches a different part of the target moment) or swarm (everyone sketches the same target). Default is swarm for v0.1 Design Sprints; divide is for teams running their second sprint with the same target who want to broaden coverage.
- Four-step sketches from each team member: Notes (20 min reviewing Monday output + lightning demos), Ideas (20 min rough doodles), Crazy 8s (8 minutes, 8 variations of the strongest Idea), Solution Sketch (30-90 min final 3-panel storyboard-style sketch).
- Recruiting tracker update: Riley (or the recruiter) confirms Friday slots; surfaces any cancellations and triggers buffer-slot activation if needed.
See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for the Brainshelf book-catalog Tuesday artifact.
Tuesday Time Structure
The full Tuesday workshop is approximately 7 hours (09:00-12:30 + 13:30-17:00). The skill's bundled artifact emerges across the day:
- 09:00-09:15: Welcome + Monday recap + Tuesday agenda
- 09:15-10:45: Lightning demos (each person 3 demos x 3 min + 1 min Facilitator extraction = ~12 min per person; 4-person team = ~50 min; 7-person team = ~85 min)
- 10:45-11:00: Break
- 11:00-11:30: Sketch assignment plan + Notes step (each person silently reviews Monday output and lightning demo board)
- 11:30-12:30: Ideas step (each person silently doodles ideas in their notebook or Figma frame)
- 12:30-13:30: Lunch + (in parallel) recruiting tracker check-in
- 13:30-13:40: Crazy 8s (8 minutes, 8 variations of strongest Idea)
- 13:40-15:30: Solution Sketch (final 3-panel sketch; everyone silent; Facilitator times)
- 15:30-15:45: Break
- 15:45-16:30: Sketches collected + named + photographed for Wednesday board; sketcher attribution hidden (Wednesday's heat-map is blind)
- 16:30-17:00: Day-end check-in; confirm sketches uploaded; confirm Wednesday morning attendance
This skill's 180-minute timebox covers the Facilitator-led portions (lightning demos + assignment + collection). The silent sketch steps (Notes, Ideas, Crazy 8s, Solution Sketch) are individual work and run in parallel; the team is together in the room (or video call) but not collaborating.
Show full SKILL.md (375 more words)Show less
Common Pitfalls
- Group brainstorming. The single most common failure mode. The Sprint method explicitly forbids group sketching because it produces sketches that converge on the loudest voice, not the best idea. Facilitator's job is to enforce silence during sketch steps.
- Sketches not concrete enough. A solution sketch must be understandable Wednesday morning WITHOUT the artist explaining it. If the heat-map team has to ask "what is this?", the sketch failed the readability bar.
- Skipping lightning demos. Lightning demos are not optional warm-up; they inject outside patterns the team would not have generated. Skipping them produces inward-looking sketches.
- Demo facilitator failing to extract reusable patterns. Each demo's reusable pattern must be captured (not the whole demo). "Spotify's home screen" is not a pattern; "feed of personalized cards with one-tap action" is.
- Sketching the prototype. The solution sketch is a concept; the prototype is Thursday's build. Sketches that try to be the prototype are over-detailed in the wrong dimensions (visual polish, copy) and under-detailed in the right ones (interaction sequence, user reaction).
- Sketcher attribution leaked into Wednesday heat-map. Wednesday's heat-map is blind (no sketcher names visible) so the team votes on the sketch, not the sketcher. If sketches arrive on Wednesday with names attached, the Facilitator strips them.
Cross-Skill Usage
Prerequisites: tool-design-sprint-map-and-target. Sketch consumes Monday's target moment as the design target for the four-step sketch protocol. Without a target moment, sketches diverge with no shared direction.
This skill does NOT invoke tool-note-and-vote. Tuesday has no voting moment; all voting happens Wednesday after sketches are produced.
Next invocation in the sprint: tool-design-sprint-decide-and-storyboard Wednesday morning.
Canonical Sources
- Knapp, J., Zeratsky, J., and Kowitz, B. Sprint. Simon and Schuster, 2016. Tuesday chapter (Chapters 8-10), particularly the four-step sketch protocol (Chapter 9).
- GV Design Sprint Guide. "Sprint Week Tuesday." https://www.gv.com/sprint/
- Character Capital. "Design Sprint Day 2." https://www.character.vc
- Google Design Sprint Kit. "Tuesday agenda template + four-step sketch handout." https://designsprintkit.withgoogle.com/
Decider Checkpoint
This skill ends with a Decider Checkpoint in references/TEMPLATE.md. There is NO mid-day Tuesday decision; the Decider's role Tuesday is to be a sketcher among other sketchers (the Decider sketches independently like everyone else). The end-of-Tuesday Decider Checkpoint is a logistics confirmation: all sketches collected, attribution stripped, Wednesday morning attendance confirmed. The substantive Decider call comes Wednesday morning at the supervote.
© 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-sketch 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 Sketch 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 Design Sprint Sketch this skillproduct-on-purpose/pm-skills | 716 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Sprint Planphuryn/pm-skills | 27k | — | ~590 | Automated safety check: Pass | MIT | |
| Structured Datathedaviddias/Front-End-Checklist | 74k | — | ~420 | Automated safety check: Pass | MIT | |
| Bio Structural Biology Modern Structure PredictionFreedomIntelligence/OpenClaw-Medical-Skills | 3.1k | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| 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
Structured Data
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup.
Bio Structural Biology Modern Structure Prediction
FreedomIntelligence/OpenClaw-Medical-Skills
Predict protein structures using modern ML models including AlphaFold3, ESMFold, Chai-1, and Boltz-1.
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.
Sketch
bergside/awesome-design-skills
A friendly, hand-drawn sketch interface inspired by pencil illustrations on warm cream paper.
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 Design Sprint Sketch
What does Tool Design Sprint Sketch do?
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Tool Design Sprint Sketch is an agent skill from product-on-purpose/pm-skills. Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch).
How do I install Tool Design Sprint Sketch in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-sketch -a claude-code`. Or copy the skill folder (skills/tool-design-sprint-sketch in product-on-purpose/pm-skills) into .claude/skills/tool-design-sprint-sketch in your project. Claude Code loads it when a task matches its description.
How do I install Tool Design Sprint Sketch in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-sketch -a codex`. Or copy the skill folder (skills/tool-design-sprint-sketch in product-on-purpose/pm-skills) into .agents/skills/tool-design-sprint-sketch in your project. Codex loads it when a task matches its description.
Can I use Tool Design Sprint Sketch 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-sketch -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-sketch, .gemini/skills/tool-design-sprint-sketch, .github/skills/tool-design-sprint-sketch and .opencode/skills/tool-design-sprint-sketch in your project.
What does Tool Design Sprint Sketch need to run?
SKILL.md names no scripts, command-line tools or credentials: Tool Design Sprint Sketch is instructions for the agent only.
Does Tool Design Sprint Sketch access the network?
SKILL.md names 3 domains. As links in the text: gv.com, character.vc and designsprintkit.withgoogle.com. This is read from the text; nothing was executed.
Is Tool Design Sprint Sketch 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 Sketch use?
Tool Design Sprint Sketch 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 Sketch use?
About 2.1k tokens (SKILL.md is roughly 8.5k 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 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Tool Design Sprint Sketch?
Skills that share tags, products or a category with Tool Design Sprint Sketch: Sprint Plan (phuryn/pm-skills, 27k stars), Structured Data (thedaviddias/Front-End-Checklist, 74k stars), Bio Structural Biology Modern Structure Prediction (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k 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 Design Sprint Sketch?
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.