菜单
Specify WHAT must be true as a delta against the current specs — testable requirements and acceptance scenarios in the OpenSpec delta format. Use after clarify; the spec, not the code, is the source of truth for behaviour. Avoid HOW (that is design).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.
Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.
Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.
Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.
Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.
Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.
| name | aiws-sdd-spec |
| description | Specify WHAT must be true as a delta against the current specs — testable requirements and acceptance scenarios in the OpenSpec delta format. Use after clarify; the spec, not the code, is the source of truth for behaviour. Avoid HOW (that is design). |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","source":"aiws@0.53.0","version":"1.0"} |
Capture WHAT must be true in the change's spec.md. Requirements with acceptance scenarios.
specs/ baseline this change deltasspec.md## ADDED Requirements / ## MODIFIED Requirements / ## REMOVED Requirements### Requirement: <name> stating the rule in RFC 2119 terms (MUST / SHOULD / MAY)#### Scenario: <name> — GIVEN … WHEN … THEN …[NEEDS CLARIFICATION: …] inline for anything still openspecs/[NEEDS CLARIFICATION] remain; success criteria are measurable; describes WHAT, never HOWspec.md.Artifacts live in
docs/development/changes/<change>/and are versioned in git. Follow the SDD lifecycle in AGENTS.md and_shared/aiws-sdd-convention.md.