design-sprint · podo — Claude Code skill: feature plans and installation
The design-sprint skill researches a codebase, drafts a feature plan, and proposes a parent issue with dependent sub-issues. It creates GitHub or Backlog issues only after you approve the content.
MIT 212 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill design-sprint -a claude-codeWhat design-sprint does
The agent reads the repository and prepares a Markdown plan with research, design, open questions, and a proposed issue split. You annotate the file, and the agent revises it. Once you give final approval, it creates a parent issue and dependent sub-issues, then adds research findings as an issue comment.
The installed upstream skill is named create-issue; it includes the earlier design-sprint workflow. GitHub issue creation requires an installed, authenticated gh CLI. For Backlog, authenticate the bee CLI. Nothing is published before your approval. There is also a name collision with wondelai-skills: installing both can overwrite the earlier design-sprint installation.
What it helps with
- research a repository before shaping a feature
- collect plan feedback inline in a Markdown file
- turn a feature proposal into a parent issue and dependent sub-issues
- create tracker issues only after reviewing their exact content
Example prompts for the agent
- Run a design sprint for this feature: inspect the repository and draft a Markdown plan.
- Break this feature proposal into a parent issue and dependent sub-issues.
- Revise the plan using my inline notes, then prepare GitHub issues for approval.
How to install design-sprint
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-sprint -a claude-code2Manually: put the files in place
~/.claude/skills/design-sprint/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-sprint/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-sprint -a codex2Manually: put the files in place
.agents/skills/design-sprint/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-sprint -a cursor2Manually: put the files in place
.cursor/skills/design-sprint/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/design-sprint2Manually: put the files in place
.github/skills/design-sprint/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-sprint -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/design-sprintManually: put the files in place
.devin/skills/design-sprint/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-sprint -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-sprint
How do I install design-sprint in Claude Code?
Run npx skills add podo/design-agent-skills --skill design-sprint -a claude-code. The skill file is installed at ~/.claude/skills/design-sprint/SKILL.md.
What does design-sprint do?
It researches your repository, drafts a feature plan for you to annotate, then proposes a parent issue with dependent sub-issues. The issues are created only after your approval.
What do I need to create GitHub or Backlog issues?
For GitHub, install and authenticate the gh CLI. For Backlog, authenticate the bee CLI. The workflow is provided by the upstream create-issue skill.
Source text
SKILL.md · MIT
--- name: design-sprint description: | 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. triggers: - "design sprint" - "feature design sprint" - "design and decompose" - "design-sprint" - "design to issues" - "feature breakdown issues" das: type: package category: product-pm upstream: "https://github.com/aoshimash/skills" upstream_path: "plugins/aoshimash-skills/skills/create-issue/SKILL.md" version: latest --- # design-sprint > Catalogue stub — full skill: [aoshimash/skills](https://github.com/aoshimash/skills) (`create-issue`) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **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 as `create-issue`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/design-sprint ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add aoshimash/skills --skill create-issue -g -y ``` **Project:** ```bash npx skills add aoshimash/skills --skill create-issue -y ``` > **Claude 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-skills ``` **Heads-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-sprint` is also written by `wondelai-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) or `wondelai-skills` (Knapp's Design Sprint skill) - PM discovery without code → use `deanpeters-pm-skills` or `pm-skills` - Feature planning without issue creation → use `plan-design-review` - Implementing the issues afterwards → upstream's separate `implement-issue` skill (not installed by this pointer)
© podo · MIT · podo/design-agent-skills
Similar skills
All skills for Design →design-sprint by other authors comes first.