メニュー
SPDD code→prompt sync — fold non-behavioural code changes back into the REASONS Canvas and report spec↔code drift. Propose-and-review, never auto-apply. Trigger: code was refactored/fixed and the spec must catch up, or to check drift.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | aiws-sdd-spec-sync |
| description | SPDD code→prompt sync — fold non-behavioural code changes back into the REASONS Canvas and report spec↔code drift. Propose-and-review, never auto-apply. Trigger: code was refactored/fixed and the spec must catch up, or to check drift. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
In SPDD the REASONS spec in {{paths.specs}}/ is the source of truth. This skill handles the
code → prompt direction of the closed loop — folding non-behavioural code changes (refactors,
renames, extracted helpers, bug fixes) back into the Canvas so it never becomes an outdated historical
record. It also reports drift: where code and spec disagree.
Direction matters. Behaviour/logic changes go the other way — fix the prompt first: edit the Canvas, then propagate with
aiws-sdd-code-maintenance. Use this skill only for code-side changes that do not change intent.
{{paths.specs}}/): map files/components to the
Canvas's Structure (§S) and Operations (§O).aiws-sdd-code-maintenance, prompt-first).aiws-sdd-code-maintenance).{{paths.changes}}/<change>/.Invoke via /sdd-sync.
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.