菜单
Use when a system has changed and its blueprint needs to reflect the change — new behaviour, modified flows, revised rules, or resolved questions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
A living product specification skill. Use when you want to document how a system works, capture user stories and flows, build shared vocabulary, discuss existing functionality, or create a single source of truth for a feature or product area.
Use when reviewing an existing blueprint for gaps, missing flows, terminology conflicts, coverage of error cases, or untestable requirements.
Use when a system already exists but is not documented — to capture how it actually works, build shared vocabulary around it, and produce a living spec that the team can reason about and discuss.
Use when building a blueprint from scratch through conversation — specifying a new feature, capturing a planned system, or turning stakeholder descriptions into a structured living spec.
Use when evaluating a proposed change to a system described in a blueprint — a new feature, behaviour change, rule modification, or scope expansion. Convenes the review panel.
Use when reviewing a draft or existing blueprint for quality — missing scenarios, terminology gaps, unclear requirements. Convenes the review panel for a structured debate.
| name | update |
| description | Use when a system has changed and its blueprint needs to reflect the change — new behaviour, modified flows, revised rules, or resolved questions. |
Incrementally update an existing blueprint after a system change. Read only affected sections, make targeted edits, record the change — without rewriting the entire blueprint.
Inputs: blueprint directory path, description of what changed.
Open README.md: current state, sections, version, completion tier.Output: updated section files, updated changelog.md, updated decisions.md (if applicable), updated README.md manifest.
