plugin-migrate

Migrates legacy SDD Devkit project content to the current structure and templates.

Updated May 8, 2026
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill plugin-migrate-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-migrate
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/plugin-migrate
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill plugin-migrate-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After updating the SDD Devkit plugin, projects often contain files, folders, and settings left in the structure of older versions, which the rest of the catalog can no longer read correctly. This Skill detects that legacy content structurally, proposes a migration plan, and normalizes it to the current layout without rewriting user content. ## Core Features & Use Cases - Structural detection: Scans the project against the current layout and templates to find outdated harness files (AGENTS.md, MEMORY.md, ADR/standards indexes), obsolete settings.json keys, old docs/specs/ layouts, legacy glossary paths, and outdated user-story headers. - Confirmed, lossless migration: Presents all findings in a single confirmation batch, applies approved changes with git mv, preserves existing identifiers exactly, and never rewrites or invents user content. - Reference rewriting and reporting: Updates internal links pointing to moved paths and reports the full old-to-new mapping, including items that require a dedicated owning skill. - Use Case: After upgrading the plugin, ask the agent to normalize the project; it finds an old docs/specs/user-stories/ folder and a legacy CLAUDE.md pointer, proposes moving them to the new changes/ layout and merging content into AGENTS.md, then applies everything after your approval. ## Quick Start Ask the agent to migrate and normalize the project content to the current SDD Devkit plugin structure after updating the plugin.

Frequently Asked Questions about plugin-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my project after updating the SDD Devkit plugin?▼

Invoke the plugin-migrate skill directly by asking to migrate or normalize the project. It scans for legacy structures, presents a single batched plan of findings and changes, and applies only what you approve, preserving all identifiers and wording.

What does the plugin migration detect and normalize?▼

It detects harness files out of template format, obsolete settings.json keys like basePath/archivePath, old docs/specs/ layouts, legacy glossary paths, technical docs in old structures, outdated user-story headers, and inherited CLAUDE.md pointer files.

Does the migration rewrite or renumber my existing content?▼

No. Migration only moves, renames, and reformats content into the current structure. Existing identifiers like MD-01 or ADR-XXX are kept exactly as issued, and user wording is never rewritten, summarized, or translated.

Can other SDD Devkit skills migrate legacy content themselves?▼

No. Other skills only work on the current structure; when they detect content from an older version, they stop and delegate to plugin-migrate, which is the sole owner of all migration logic in the catalog.

What happens if I decline part of the migration plan?▼

Declined items are left untouched and recorded in the closing summary with their consequence: the rest of the catalog may not read them correctly. The skill will not re-propose a declined migration within the same invocation.