菜单
Use when the user wants to change specs/constitution.md. Constitutional changes go in their own commit, with explicit justification, separate from feature work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | update-constitution |
| description | Use when the user wants to change specs/constitution.md. Constitutional changes go in their own commit, with explicit justification, separate from feature work. |
You are about to amend the constitution. Constitution changes are deliberate and rare.
Read the current specs/constitution.md in full.
Confirm the proposed change with the user. Ask:
architecture.md, conventions.md, CI tests, mkdocs pages) need to follow?Apply the change to specs/constitution.md. Keep it short — the constitution is supposed to grow slowly. If a rule is more conditional than absolute, suggest moving it to conventions.md instead.
Update downstream artifacts the user identified.
Stage and commit separately. Constitutional changes do not blend into a feature commit. Recommended commit message format: [constitution] <short summary>.
conventions.md (strong preference) or roadmap.md (planned).Stage 5 of the spec-driven workflow — archive a shipped feature. Run this only once every task in the feature's tasks.md has shipped AND you are satisfied the work is done (typically after review, and when PR is ready to open). It promotes any durable insight into the live reference specs, then deletes the spec folder. It never writes an archive summary file. Invoke explicitly; it is not auto-chained from feature-implement.
Orchestrate the full implementation of a feature's tasks.md end to end. A supervisor agent loops over every uncompleted task, spawning an implement sub-agent then a review sub-agent, triaging the review findings with its own judgement — auto-approving the evident fixes and escalating only genuinely structuring decisions to the user via AskUserQuestion — applying the fixes, and continuing to the next task. Use when you want to drive a whole feature with minimal human intervention, surfacing only the decisions that genuinely need you.
Use to execute a single task from an approved tasks.md. Fourth stage of the four-stage spec-driven workflow. Reads spec.html, plan.html, tasks.md, then implements one task at a time, respecting constitution gates.
Use after the user approves a spec.html to write or refine the corresponding plan.html. Second stage of the four-stage spec-driven workflow. Plan answers HOW the spec becomes code; respects architecture.md. Still no code execution.
Use when the user wants to start a new feature in this repo. Walks the agent through writing specs/features/<feature-name>/spec.html — the first stage of the four-stage spec-driven workflow (specify → plan → tasks → implement). Read-only on code. May also draft plan.html in the same pass when the kickoff is design-rich.
Use after the user approves a plan.html to break it into ordered, independently-shippable tasks. Third stage of the four-stage spec-driven workflow. Output is tasks.md; still no code execution.