メニュー
Migrate a legacy non-Git SDD workspace (`_vN` filenames + `sdd_docs/`) to the unified Git-based model. Trigger: adopting this generator on a repo built with standalone, pre-Git SDD plugins.
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-migrate |
| description | Migrate a legacy non-Git SDD workspace (`_vN` filenames + `sdd_docs/`) to the unified Git-based model. Trigger: adopting this generator on a repo built with standalone, pre-Git SDD plugins. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
Migrate a workspace built with standalone, pre-Git SDD plugins (no-Git v1) to this generator's
unified model: _vN filename versioning → Git, and the parallel sdd_docs/ trail → the single
{{paths.development}}/ store. One-time, opt-in, advanced/IT use — not forced on anyone.
_vN-suffixed specs (e.g. specs/001-foo_v3.md), a specs/archive/ folder, and/or a sdd_docs/ folder.
If the repo already uses {{paths.specs}}/<NNN>-<slug>.md + Git, there is nothing to migrate.Require a clean git working tree (commit/stash first) — Git is the safety net. Produce a migration plan and show it; proceed only on explicit confirmation. Do every step as its own reversible commit.
_vN → Git. Per spec_id, keep the highest-version file as the canonical
{{paths.specs}}/<NNN>-<slug>.md (drop the _vN suffix). The version history already lives in §0 Changelog;
the old _vN + specs/archive/ copies become Git history — remove the duplicates in the migration
commit (recoverable via Git). Preserve each spec's frontmatter status.sdd_docs/ trail → unified store. The per-skill trail files carry process notes: fold durable
decisions into {{paths.status}}/PROJECT-STATE.md and any in-flight context into {{paths.changes}}/<change>/.
Then remove sdd_docs/.aiws-sdd-spec-review drives transitions over Git (no _vN).sdd.schema: reasons (+ appProfile if applicable) in workspace.config.yaml; run
ai-workspace sync to project AGENTS.md + skills.archive/ + sdd_docs/ removed.git log shows the migration commits; specs validate against aiws-sdd-spec-schema; run sdd-audit-* before sign-off.