issue-to-branch-start

To create a git branch from an issue with deterministic naming, start implementation from the finalized planning issue. This workflow creates or reuses a linked branch with a concise, predictable name and reports its creation or reuse status.

Linking a git workflow branch to a planning issue requires a finalized plan or a canonical plan marker. The workflow enforces deterministic branch naming, connects the branch to the source issue, and ensures you begin coding from the canonical issue context.

Yes, you need a clean working tree before starting implementation from a new branch. The workflow validates the working tree state before creating or reusing the linked branch, ensuring a predictable base for your deterministic branch name.

If a branch linked to an issue already exists when starting implementation, the workflow reuses the existing branch. It reports the reuse status and the base branch, preventing duplicate branches and maintaining deterministic naming across your git workflow.

No, you cannot start implementation without a finalized planning issue or canonical plan marker. This workflow is applicable only when a plan exists, ensuring the branch context is fully established before creating the deterministic branch name.