phase-init

To create a phase specification, instantiate a template artefact into docs/specs/<feature-id>/<phase>-spec.md by providing the phase and feature-id, which creates the directory as needed and refuses to overwrite existing files.

When a spec already exists, the artefact generation process refuses to overwrite it and reports that the specification already exists, preserving your existing phase artefacts safely.

You generate separate requirements, design, or test specifications when you need to instantiate structured phase artefacts from a Programme bundle template into a feature's dedicated docs/specs directory.

Start writing phase specs by executing the instantiation command with your selected phase and feature-id, which validates the inputs and writes the corresponding phase-spec.md file into the correct directory.

No, the phase artefact generator does not overwrite existing phase docs; it enforces input validation and safely preserves existing specifications by refusing to write over them.

The best way to manage feature specifications across SDLC phases is generating standardized artefacts from templates into a unified docs/specs/<feature-id> directory, ensuring existing specs remain preserved.