メニュー
Start a new design cycle. Creates cycle scope in STATE.md, initializes .design/CYCLES.md entry. Each cycle has its own goal and tracks its own decisions/tasks/pipeline runs.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hegemonart/get-design-done --skill gdd-new-cycleコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Master design pipeline for Claude Code. 5-stage workflow: Brief → Explore → Plan → Design → Verify. Run 'brief' first in any new project to capture the design problem, then 'explore' to inventory the codebase and interview for context. Invoke without arguments for status and auto-routing.
Run the pipeline with optional agents skipped for speed. Skips: phase-researcher, design-assumptions-analyzer, design-integration-checker. Keeps: planner, executor, verifier, auditor. Activates for requests involving a lightweight design pass, a fast iteration, or a quick low-ceremony change.
Routes a /gdd command to fast|quick|full path + S|M|L|XL complexity_class and returns {path, complexity_class, model_tier_overrides, resolved_models, estimated_cost_usd, cache_hits}. A SKILL.md prompt the model executes to emit a routing-decision JSON from rule tables (no separate agent spawn). Optional/advisory - invoked only by the skills that opt into routing; the budget-enforcer hook tolerates its absence. Read by hooks/budget-enforcer.ts.
SOC 職業分類に基づく
SKILL.md を表示中
| name | gdd-new-cycle |
| description | Start a new design cycle. Creates cycle scope in STATE.md, initializes .design/CYCLES.md entry. Each cycle has its own goal and tracks its own decisions/tasks/pipeline runs. |
| argument-hint | [<goal>] |
| tools | Read, Write, AskUserQuestion |
The cycle is the hierarchical unit above individual pipeline runs: Cycle > Pipeline run > Wave > Task. Each cycle has a goal, tracks its own decisions, and can span many pipeline runs. /gdd:complete-cycle closes the cycle once goals are met and a retrospective is captured.
Read .design/STATE.md. If cycle: field is populated and no complete flag, ask: "Cycle is active. End it first with /gdd:complete-cycle?" Abort if user declines.
If no goal was passed as an argument, ask (AskUserQuestion): "What is the goal for this design cycle? (e.g., 'Redesign the checkout flow', 'Improve dashboard accessibility')"
Generate cycle ID: read .design/CYCLES.md if present, find the max cycle-N, increment. If CYCLES.md is missing, start at cycle-1.
Update .design/STATE.md frontmatter: set cycle: cycle-N.
Create or append to .design/CYCLES.md:
## cycle-N: <goal>
**Started**: <date>
**Status**: active
**Goal**: <goal>
**Pipeline runs**: 0
**Decisions made**: 0
Reset the <decisions> section in STATE.md for the new cycle. Preserve prior decisions by prepending a comment marker <!-- prior cycle decisions archived in CYCLES.md -->.
Print: "Cycle cycle-N started. Run @get-design-done brief or @get-design-done explore to begin."
/gdd:complete-cycle.