maestro-phase-add

Inserting a new phase requires a phase name and an optional --after or --before flag to determine positioning. The system validates inputs, checks for duplicate slugs, creates the phase directory, and updates index.json, roadmap.md, and state.json accordingly.

Renumbering phases updates the internal state.json file to reflect the modified sequence and new phase addition. This ensures the project state remains synchronized with the roadmap.md content and the directory structure.

Adding a project phase automatically creates the directory with an initialized index.json and inserts the phase into roadmap.md at the correct position. This eliminates manual updates to index files and roadmap markdown content.

Yes, the tool validates inputs and checks for duplicate slugs before modifying the roadmap. It provides clear error handling to prevent naming conflicts and maintain project roadmap integrity.

Phased roadmaps are stored under the .workflow/phases directory structure and use zero-padded two-digit phase numbers. This format ensures proper alphabetical sorting and consistent numbering across index files and roadmap content.