shine-add-phase

To append a new phase to a milestone in a roadmap, you can use an automated workflow that calculates the next sequential integer, generates a directory slug, and updates the ROADMAP state to ensure consistency and traceability.

Adding sequential phase numbers to roadmap milestones involves parsing arguments, verifying milestone existence, calculating the next integer phase number, and routing the workflow to insert the new phase entry into the correct directory.

Slug generation for a new phase directory creates a readable identifier for the phase folder. It is triggered during the add-phase workflow, ensuring the directory structure aligns with the new phase entry inserted into the roadmap.

Yes, you need an existing milestone. The add-phase workflow enforces milestone existence checks before calculating the next phase number, generating slugs, and updating the STATE.md file to reflect the new phase.

The best way to automate roadmap state updates is using a workflow that handles phase numbering and directory creation, then directly evolves the ROADMAP state tracking within the STATE.md file to maintain structural consistency.

Automated phase creation may fail to update the roadmap state if the milestone existence check fails or if argument parsing encounters an error, preventing proper workflow routing to the add-phase process and STATE.md updates.