菜单
Installs the Codex-side SDD agent TOML files from the plugin bundle, reminds the user to trust hooks, and verifies that the SDD gates bite after plugin install.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | spec-setup |
| description | Installs the Codex-side SDD agent TOML files from the plugin bundle, reminds the user to trust hooks, and verifies that the SDD gates bite after plugin install. |
Run this once after installing the sdd Codex plugin. Codex plugins can bundle skills
and hooks, but there is no official bundled mechanism for agents/*.toml, so this skill
guides the agent TOML copy step.
Source files live in the installed plugin at:
${PLUGIN_ROOT}/agents/*.toml
Destination:
~/.codex/agents/
Process:
${PLUGIN_ROOT} to the installed sdd plugin root. If it is not available in
the current execution environment, stop and report that exact observation instead of
guessing a path.~/.codex/agents/ if it does not exist.${PLUGIN_ROOT}/agents/*.toml:
Do not silently overwrite existing agent files.
Plugin-bundled hooks are still non-managed hooks. After plugin install, open the Codex
TUI once and trust the SDD hooks in the hooks browser. codex exec --dangerously-bypass-hook-trust is for smoke tests only; it is not a persisted trust
step.
After trusting hooks, verify the gate bites before relying on the workflow. In a bare
temporary project with no spec/changes/, submit:
$spec-apply implement x
Expected result: Codex blocks the prompt with an SDD gate message before implementation starts.
Interrogates 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.