菜单
Full SDD workflow, end to end. Runs everything from research through archive automatically; MUST stop at interrogation points and MUST stop at HARD GATE. Also accepts the legacy $sdd entry point. Trigger words: spec first / proposal / design first / draft a plan.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | spec-workflow |
| description | Full SDD workflow, end to end. Runs everything from research through archive automatically; MUST stop at interrogation points and MUST stop at HARD GATE. Also accepts the legacy $sdd entry point. Trigger words: spec first / proposal / design first / draft a plan. |
Task: $ARGUMENTS
Large changes (>150 lines / touching 3+ files / introducing new dependencies / architectural decisions). Trivial / small / medium tasks should be handled directly — NEVER activate this workflow for those.
Invoke each phase command in the order below. If any phase encounters user rejection or a placeholder scan / HARD GATE failure → stop and report; do not push through.
$spec-research <direction> — survey industry practices + key constraints + flag [TBD] pending decisions$spec-ask — work through each [TBD] one by one by presenting numbered options to the user; move answered items to ## Decided
$spec-design is needed — trigger if any one applies:
$spec-propose — write the four-section proposal.md
[TBD] placeholders$spec-apply (apply auto-appends APPROVED; no "reply go" step needed)$spec-revise [section] (minor adjustments) or $spec-chat (rethink the direction)$spec-apply — implement the code, advancing through proposal / tasks
$spec-verify — spawns the independent spec-verifier agent (three dimensions + charter audit, ledger round)$spec-archive$spec-chat — enter discussion mode; no documents are touched$spec-ask — run another interrogation round (for newly surfaced [TBD]s)$spec-research <new direction> — re-survey; existing artifacts are snapshotted, not deleted$spec-status — check which phase you are currently inInterrogates preference-driven decision points. Works through each [TBD] in research.md one by one as numbered plain-text questions; answered items are moved to
Spec-driven development workflow overview. Load this skill when the user says "spec this first / draft a proposal / design first / write a proposal", or when a task is >150 lines / spans 3+ files / introduces a new dependency / involves an architecture choice — to learn the sdd plugin's 11 commands, artifact map, and Shared Principles (HARD GATE / interrogation / Stuck Protection / Anti-Cheating).
Implement the code, advancing by proposal/tasks. A pre-command hook checks that proposal.md carries the required prerequisites. Incremental verification: call $spec-verify close to each node as it lands, don't save it all for the end.
Dispatches a researcher agent to survey industry practices and key constraints, writing findings into research.md (single file; Open[TBD]/Decided maintained as before). Changing direction = snapshot the current research.md into the research/ discarded-draft pile first, then overwrite with the new direction; old drafts can be resurrected at any time.
Verifies the current change by dispatching the independent spec-verifier agent (fresh context — the implementing conversation never audits itself) across three dimensions + charter audit. Every run updates the verification ledger spec/changes/<name>/verify.md (stable finding IDs + round diffing + unfixed-escalation). Can be re-run independently.
Archives the current change to spec/archive/YYYY-MM-DD-<name>/. Only invoked when the user explicitly says "archive". Writes an archive-stage retrospect, checks for uncommitted code, and is guarded by the check-archive hook.