菜单
Propagate a REASONS spec change into existing code — diff old vs active spec, classify each change, apply with per-change confirmation. Trigger: code must follow an edited spec.
用 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-code-maintenance |
| description | Propagate a REASONS spec change into existing code — diff old vs active spec, classify each change, apply with per-change confirmation. Trigger: code must follow an edited spec. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
When a spec changes, bring the code back in sync. Diff the previous spec revision (Git history) against the
active spec in {{paths.specs}}/, classify each entity/operation/dependency/flag delta as add / modify /
remove, and apply it with per-change confirmation.
aiws-sdd-code-generation's patterns for the add/modify cases; keep the layer ordering.aiws-sdd-test-generation to re-derive its tests.Append the change set (per-change verdict, files + SHA-256) to {{paths.changes}}/<change>/. The spec stays the
source of truth — if the code and spec disagree, fix the spec first.