How do I install the Design Sprint skill?

Run npx skillmds add podo/design-sprint in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Design Sprint safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Design Sprint?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Design Sprint free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Design Sprint?

podo (@podo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Design Sprint by podo — Agent Skill

Name: Design Sprint
Rating: 4.5 (4 reviews)
Author: podo

Design Sprint

Deeply researches a codebase, designs a feature through iterative brainstorming and annotation cycles, then decomposes it into an implementable issue hierarchy (parent + sub-issues with dependencies) on GitHub or GitLab. Hard gates between phases ensure research happens before design, and design is complete before implementation. Each sub-issue is scoped to require zero creative decisions.

podo 6853571 2 files · 2.3 KB Updated Sep 9, 2026

File contents

design-sprint

Catalogue stub — full skill: aoshimash/skills

Install the full skill

Install via Claude Code plugin:

/plugin install aoshimash/skills

Or clone directly:

# Global
git clone https://github.com/aoshimash/skills /tmp/aoshimash-skills
cp -r /tmp/aoshimash-skills/plugins/aoshimash-skills/skills/design-sprint \
  ~/.agents/skills/design-sprint

# Project
cp -r /tmp/aoshimash-skills/plugins/aoshimash-skills/skills/design-sprint \
  .agents/skills/design-sprint

What it does

A structured 4-phase workflow that bridges design and implementation:

Phase	Output
0 — Setup	Detect issue tracker (GitHub/GitLab), confirm scope
1 — Research	Deep codebase reading → written research artifact (not verbal summary)
2 — Design	Brainstorm feature → local markdown plan → annotation cycles with user
3 — Decompose	Plan → parent issue + sub-issues, each implementable with zero creative decisions
4 — Create	Push issue hierarchy to tracker with dependencies

Core principles:

Research before design — never design without a written research artifact
Plan as shared mutable state — user annotates inline in the markdown file
Implementation must be boring — if a sub-issue requires design judgment, decompose further
Hard gates — no phase proceeds without explicit user approval

When NOT to use

Design sprint workshop facilitation (Crazy 8s, HMW, voting) → use pm-skills (Design Sprint section)
PM discovery without code → use deanpeters-pm-skills or pm-skills
Feature planning without issue creation → use plan-design-review

---name: design-sprintdescription: Deeply researches a codebase, designs a feature through iterative brainstorming and annotation cycles, then decomposes it into an implementable issue hierarchy (parent + sub-issues with dependencies) on GitHub or GitLab. Hard gates between phases ensure research happens before design, and design is complete before implementation. Each sub-issue is scoped to require zero creative decisions.--- # design-sprint > Catalogue stub — full skill: [aoshimash/skills](https://github.com/aoshimash/skills) ## Install the full skill Install via Claude Code plugin: ```bash /plugin install aoshimash/skills ``` Or clone directly: ```bash # Global git clone https://github.com/aoshimash/skills /tmp/aoshimash-skills cp -r /tmp/aoshimash-skills/plugins/aoshimash-skills/skills/design-sprint \ ~/.agents/skills/design-sprint # Project cp -r /tmp/aoshimash-skills/plugins/aoshimash-skills/skills/design-sprint \ .agents/skills/design-sprint ``` ## What it does A structured 4-phase workflow that bridges design and implementation: | Phase | Output | |---|---| | **0 — Setup** | Detect issue tracker (GitHub/GitLab), confirm scope | | **1 — Research** | Deep codebase reading → written research artifact (not verbal summary) | | **2 — Design** | Brainstorm feature → local markdown plan → annotation cycles with user | | **3 — Decompose** | Plan → parent issue + sub-issues, each implementable with zero creative decisions | | **4 — Create** | Push issue hierarchy to tracker with dependencies | Core principles: - Research before design — never design without a written research artifact - Plan as shared mutable state — user annotates inline in the markdown file - Implementation must be boring — if a sub-issue requires design judgment, decompose further - Hard gates — no phase proceeds without explicit user approval ## When NOT to use - Design sprint workshop facilitation (Crazy 8s, HMW, voting) → use `pm-skills` (Design Sprint section) - PM discovery without code → use `deanpeters-pm-skills` or `pm-skills` - Feature planning without issue creation → use `plan-design-review`

Frequently asked questions