From rad-brainstormer
Design this, create a spec, design sprint, architecture for this, write a design doc. Post-ideation: architecture, components, data flow, error handling, testing. Not for ideation — use brainstorm-session for that.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rad-brainstormer:design-sprintThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a chosen software approach into a complete, reviewable design spec ready for implementation planning.
Turn a chosen software approach into a complete, reviewable design spec ready for implementation planning.
Prerequisite: The user has already decided WHAT to build (either through brainstorm-session or by coming in with a clear idea). This skill handles HOW to design it.
Do NOT write any code, scaffold any project, or invoke any implementation tool until the design is approved by the user. This is a DESIGN skill, not an implementation skill.--non-interactive mode, skip approvals and mark unconfirmed sections in awaiting_user_review.This skill honors two mode flags when passed in the invocation:
--non-interactive — Skip user-approval gates. Produce a best-effort design doc, write it to the default in-project path (no commit), and emit a trailing JSON block listing awaiting_user_review items. For agent/CI callers that deadlock on interactive menus.--resume <run-id> — Load checkpoint state from .brainstorm/state/<run-id>.json and continue from the last saved step.Save state to .brainstorm/state/<run-id>.json at these transitions:
Checkpoint schema is the same as brainstorm-session (see that skill for the full JSON shape) with skill: "design-sprint" and phase values 1 | 2 | 5 | 6-<section> | 7 | 8-iter-N.
On --resume <run-id>, load the file, announce the step you're resuming from, and continue without re-running completed steps.
Complete these steps in order:
docs/design.md if present — that file is the project's brand / UI/UX design direction; honor it as a constraint, never write to it)<path>. Please review and let me know about any changes."/rad-planner:plan for implementation planning (see "After the Design" below)One self-contained markdown file — ask the user where, with two sensible options:
docs/ (suggest
docs/YYYY-MM-DD-<topic>-spec.md), with a header marking it transient:
"Design spec — consumed by /rad-planner:plan; archive after planning." The
repo's doc-hygiene tooling (rad-repo-manager) will later flag it for archiving —
that's the designed lifecycle. Never write to docs/design.md: that file is
the project's brand / UI/UX design direction, not a technical spec.~/Documents/Brainstorms/YYYY-MM-DD-<topic>-spec.md; on Claude Desktop / Cowork,
also surface the file so it can be saved or downloaded directly.Use clear, concise language. Never auto-commit — the user commits via their normal flow.
Dispatch the spec-reviewer agent with the substituted references/subagent-prompts/spec-review.md template, passing the current iteration and max_iterations (default 5) and any prior iteration's blocking_issues. Parse the JSON response:
status: approved → proceed to user review gatestatus: issues_found and iteration < max_iterations → fix the blocking issues, increment iteration, re-dispatchescalation_required: true (or iteration >= max_iterations with issues remaining) → stop looping. Surface the unresolved_issues JSON to the user with: "Spec review hit iteration cap with unresolved issues. Please decide: (a) accept these as known gaps, (b) rewrite the affected sections yourself, or (c) drop back to Step 5 to redesign." In --non-interactive mode, keep the current spec on disk and add the unresolved issues to awaiting_user_review.Markdown fallback is accepted from the agent — parse best-effort if JSON is missing.
"Spec written to
<path>. Please review it and let me know if you want to make any changes before we start the implementation plan."
Wait for user response. If changes requested, make them and re-run spec review.
Hand off to /rad-planner:plan to turn the approved spec into a release-map implementation plan with risk review — its discovery interview pre-fills from the spec, so the user won't be re-asked what the spec already answers. If rad-planner is not installed, surface this to the user and suggest installing it, or let the user invoke their preferred implementation-planning workflow.
Do NOT invoke frontend-design, mcp-builder, or any other implementation skill directly from design-sprint — implementation planning is a separate, reviewable phase.
npx claudepluginhub radorigin-llc/rad-claude-skills --plugin rad-brainstormerProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.