design-sprint
Skill32 starsChanged 6 months agoMITView on GitHub
Deeply researches a codebase, designs a feature through an annotated plan file, then decomposes it into an implementable issue hierarchy (parent + sub-issues with dependencies) on GitHub or Backlog. Nothing is published until you approve the exact content. Installs upstream's create-issue skill, which absorbed the earlier design-sprint skill.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
- wondelai/skillstheir own version, first seen Jul 16, 2026
- talgacapri/pm-ostheir own version, first seen May 23, 2026
- weiyongw/Skillstheir own version, first seen Mar 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- wondelai/skills★ 2.6ksame name
- razbakov/skills★ 4same name
- weiyongw/Skills★ 4same name
- Adhamxon/claude-code-skills★ 2same name
- davidanthonyn/claude-skills★ 0same name
- talgacapri/pm-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository170 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-agentsSkill
- accessibility-catalogueSkill
- addyosmani-qualitySkill
- ai-graphic-design-skillSkill
- algorithmic-artSkill
- anatomySkill
- animate-css-skillSkill
- animate-skillSkill
- anthropics-skillsSkill
- antvis-chart-skillsSkill
- apple-hig-skillsSkill
- assimovt-productskillsSkill
- awesome-design-skillsSkill
- baseline-uiSkill
- bencium-ux-designerSkill
- brand-design-mdSkill
- building-componentsSkill
- callstack-agent-skillsSkill
- cc-slidevSkill
- chadboyda-gtmSkill
- claud3Skill
- claude2figmaSkill
- claudedesignskillsSkill
- claude-pm-skillsSkill
- claude-wireframe-skillSkill
- cloudai-threejsSkill
- cloudflare-web-perfSkill
- color-expertSkill
- composio-artifactsSkill
- content-catalogueSkill
- content-strategySkill
- copywriting-skillSkill
- coreyhaines-marketingSkill
- creative-directorSkill
- css-animation-skillSkill
- d3js-skillSkill
- dark-pattern-auditSkill
- data-analysis-skillSkill
- data-viz-agentSkill
- deanpeters-pm-skillsSkill
- design-auditorSkill
- design-briefSkill
- design-catalogueSkill
- design-consultationSkill
- design-debt-auditSkill
- design-engineering-catalogueSkill
- designer-skillsSkill
- design-for-aiSkill
- design-htmlSkill
- design-impact-reportingSkill
- design-labSkill
- design-motion-principlesSkill
- design-negotiationSkill
- design-review-garrytanSkill
- design-system-governanceSkill
- design-tokens-skillSkill
- design-with-claudeSkill
- digidai-pmSkill
- dimensional-drawingSkill
- The first 60 shown.
The file
Files
design-sprint
Catalogue stub — full skill: aoshimash/skills (
create-issue)
<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->Decision tree
- Is the full skill already installed?
Upstream names this skill
create-issue, so it installs next to this pointer (the pointer is not replaced).- Global:
f=~/.agents/skills/create-issue/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" - Project:
f=.agents/skills/create-issue/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" installed→ the skill is installed ascreate-issue, invoke it and proceedpointer→ go to step 2
- Global:
Detect scope, then install:
[ -e ~/.agents/skills/design-sprint ] && echo "global" || echo "project"Global:
npx skills add aoshimash/skills --skill create-issue -g -yProject:
npx skills add aoshimash/skills --skill create-issue -yClaude Code: send a command as a chat message starting with
!to run it without leaving the conversation.
Claude Code plugin route:
/plugin marketplace add aoshimash/skills
/plugin install aoshimash-skills@aoshimash-skillsHeads-up
- Requires: gh CLI installed and authenticated (GitHub issues) or the bee CLI authenticated (Backlog issues); Creates issues on your tracker, only after you approve the exact content
- License: MIT
- Name collision:
design-sprintis also written bywondelai-skills(its install or its catalogue pointer); installing both overwrites the earlier one.
<!-- das:install:end -->Invoke after install
- Skill name:
create-issue - Trigger phrases: "design sprint", "design and decompose", "create an issue", "plan and create issues"
What it does
Upstream folded its design-sprint workflow into create-issue, which has two flows. The Lightweight Flow files a single well-scoped issue after one batched question round and one draft approval. The Design Flow is the former design sprint:
| Step | Output |
| Setup | Detect the issue tracker (GitHub or Backlog) and the repository's issue templates |
| Research and design | Deep codebase reading, then one consolidated plan file (research, design, open questions, split proposal) |
| Annotation cycle | You annotate the plan inline in the markdown file; the agent revises until it is right |
| Issue creation | After one final approval, a parent issue plus sub-issues with dependencies; research findings are kept as an issue comment |
Core principles: issues describe motivation and proposal, never implementation steps; ambiguity is resolved before an issue is created; nothing is published without explicit approval; splitting into sub-issues is always a proposal. Needs the gh CLI (GitHub) or the bee CLI (Backlog) authenticated.
When NOT to use
- Design sprint workshop facilitation (Crazy 8s, HMW, voting) → use
pm-skills(Design Sprint section) orwondelai-skills(Knapp's Design Sprint skill) - PM discovery without code → use
deanpeters-pm-skillsorpm-skills - Feature planning without issue creation → use
plan-design-review - Implementing the issues afterwards → upstream's separate
implement-issueskill (not installed by this pointer)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.