migrate-to-deltas

Migrate katachi projects from feature-centric to delta-centric development.

1|1|Updated Dec 9, 2025

Search Tags:#documentation #migrate #project-structure #delta-specs #dependency-updates #deltas

Ready to run

npx skills add https://github.com/asermax/claude-plugins --skill migrate-to-deltas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-to-deltas
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/migrate-to-deltas
Command: npx skills add https://github.com/asermax/claude-plugins --skill migrate-to-deltas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates katachi projects from a feature-centric to a delta-centric development and documentation structure, reducing manual rework and aligning teams around delta workflows.

Core Features & Use Cases

Delta scaffolding: creates delta-specs/, delta-designs/, and delta-plans/ to host delta-oriented work.
Migration flow: converts FEATURES.md to DELTAS.md and maps feature IDs to delta IDs.
Documentation reconstruction: moves feature-specs/ and feature-designs/ to delta-specs/ and delta-designs/, and generates nested delta docs with domain mappings.
Dependency modernization: updates DEPENDENCIES.md to delta IDs and removes obsolete files like BACKLOG.md.
Automation-ready: provides pre-checks and templates to guide the interactive migration.

Quick Start

Run the migrate-to-deltas skill on a katachi project to begin the delta-based migration.

Frequently Asked Questions about migrate-to-deltas

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

FAQPage Schema

How do I migrate a katachi project from feature-centric to delta-centric documentation?▼

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.

What is delta-based project structure and when do I need to restructure into it?▼

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.

How do I convert feature IDs to delta IDs during a documentation restructuring?▼

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.

Does the delta migration process remove obsolete files like BACKLOG.md from the project?▼

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.

Can I use delta scaffolding on a project without existing feature-specs and feature-designs directories?▼

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.

What are the limitations of automated delta migration for nested documentation?▼

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.