基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hegemonart/get-design-done --skill gdd-todo命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
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.
| name | gdd-todo |
| description | Design backlog - add/list/pick design tasks. Writes to .design/TODO.md. |
| argument-hint | <add|list|pick> [text] |
| tools | Read, Write, AskUserQuestion, mcp__gdd_state__get, mcp__gdd_state__add_decision, mcp__gdd_state__add_must_have |
| disable-model-invocation | true |
Role: Design todo list. Three subcommands: add, list, pick. Backing store: .design/TODO.md. For items that are pipeline-level decisions or must-haves (not free-form backlog), route through the gdd-state MCP tools instead - see Pipeline-linked items below.
# Design Todos
## P0 — Blocking
- [ ] [2026-04-18] Fix contrast ratio on card headers
## P1 — High
- [ ] [2026-04-18] Align Button focus ring with tokens
## P2 — Normal
## P3 — Nice to have
Priority is encoded by section, not inline. Status markers: [ ] unchecked, [x] done, [-] [in-progress], [p] [promoted].
If text omitted, use AskUserQuestion: "What todo item? (include priority P0-P3 if known)". Parse leading P[0-3] token from text; default P2. Append under the right section as:
- [ ] [YYYY-MM-DD] <text without priority token>
Create TODO.md from the template above if missing.
mcp__gdd_state__get → pipeline-level decisions + must-haves (shown as context at the top)..design/TODO.md (file outside the MCP catalog). Print all - [ ] and - [-] items grouped by priority section, with index numbers.Read .design/TODO.md. Collect unchecked items. Use AskUserQuestion to let the user pick one. Rewrite the chosen line as:
- [-] [YYYY-MM-DD] [in-progress] <original text>
Print "Picked: ".
When the user promotes a todo to a pipeline decision or must-have, route through MCP instead of TODO.md:
mcp__gdd_state__add_decision with { id: "D-XX", text: "...", status: "locked"|"tentative" }.mcp__gdd_state__add_must_have with { id: "M-XX", text: "...", status: "pending" }..design/.