start-implementation-phase

To transition an issue from planning to implementation, you manually invoke the skill to validate planning phase completion, announce the entry protocol, and guide the creation of a Git branch from the latest main.

Starting the implementation phase requires a target issue that has fully completed its Planning Phase (P1-P4) and an existing, ready progress file to validate readiness before proceeding.

This workflow handles Git branch creation by guiding the I1 execution step to create a new branch from the latest main, ensuring you update the progress file immediately after the step completes.

The implementation handoff requires explicit user confirmation to enforce safe transitions, prevent the silent re-execution of completed planning work, and ensure the progress file is actively updated after each step.

The entry protocol announces the workflow flow, current phase, target issue number, the associated progress file, and the current step to execute, ensuring clear context before implementation begins.

No, you cannot use this workflow without a completed planning phase. It validates that the Planning Phase (P1-P4) is finished and a ready progress file exists, blocking progression if prerequisites are unmet.