メニュー
Symptom-driven design debugger with persistent state. Phase 1 builds a feedback loop; Phase 2 hypothesizes. Writes findings to .design/DEBUG.md. Use when a symptom needs systematic, one-variable-at-a-time tracking.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hegemonart/get-design-done --skill gdd-debugコマンドは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-debug |
| description | Symptom-driven design debugger with persistent state. Phase 1 builds a feedback loop; Phase 2 hypothesizes. Writes findings to .design/DEBUG.md. Use when a symptom needs systematic, one-variable-at-a-time tracking. |
| argument-hint | [<symptom description>] |
| tools | Read, Write, Grep, Glob, AskUserQuestion, Task |
Systematic, checkpoint-driven design debugger. Loads framing from ./../reference/debugger-philosophy.md (five principles) and the feedback-loop construction catalog from ./debug-feedback-loops.md (10 priority-ordered loop paths). Phase 1 builds the loop; Phase 2 generates hypotheses. Writes every step to .design/DEBUG.md so killed sessions can resume.
reference/debugger-philosophy.md (five principles) and ./debug-feedback-loops.md (10 construction paths; iterate-on-loop discipline). Keep both in mind for the entire session..design/DEBUG.md if it exists. If there is an open session with no ### Fix Proposal block, ask: "Resume existing session '' or start a new one?".design/DESIGN-PLAN.md (goals), .design/STATE.md <decisions> block (D-XX items), and any source files pointed at by the symptom../debug-feedback-loops.md for the 10 construction paths in priority order (failing test > curl > CLI fixture > headless browser > trace replay > throwaway harness > fuzz > bisect > differential > HITL bash). Iterate on the loop itself (cache setup, narrow scope, pin time, seed RNG, isolate filesystem, freeze network) before iterating on the bug. For non-deterministic bugs: raise reproduction rate to at least 30%, not clean repro. Do not proceed to Phase 2 (hypothesis generation) until you have a loop you believe in.Form one hypothesis (one variable).
Investigate (read files, grep, measure). Re-run the Phase 1 feedback loop to confirm the hypothesis pinpoints the symptom.
Append to .design/DEBUG.md:
## <symptom> — <date>
### Hypothesis <N>
### Investigation
### Finding
Ask (AskUserQuestion): "Continue investigating? (yes / found it / dead end)"
### Fix Proposal block with a concrete patch description. Re-run the Phase 1 loop to confirm the fix flips it from fail to pass. Ask: "Create a todo with {{command_prefix}}todo add, or execute the fix now?"