migrate-to-deltas

To migrate to delta-centric documentation, run the migration skill to convert FEATURES.md to DELTAS.md, move feature-specs and feature-designs to delta directories, and update DEPENDENCIES.md with mapped delta IDs.

Delta-based project structure organizes development around incremental deltas rather than broad features. You need it when transitioning your katachi project workflows to delta-centric development to reduce manual rework and align teams.

Converting feature IDs to delta IDs happens automatically during migration. The process maps existing feature identifiers from FEATURES.md to corresponding delta IDs in the new DELTAS.md file while preserving the original references.

Yes, delta migration removes obsolete files like BACKLOG.md. It modernizes the project by updating DEPENDENCIES.md to reference delta IDs and cleaning up deprecated documentation from the previous feature-centric structure.

No, delta scaffolding targets projects with existing FEATURES.md, feature-specs, and feature-designs. Pre-checks enforce these prerequisites before creating delta-specs, delta-designs, and delta-plans directories.

Automated delta migration generates nested delta docs with domain mappings and provides template prompts for guidance, but the interactive migration flow still requires manual oversight to validate the reconstructed documentation structure.