create-branch

Automating feature branch creation determines whether to create, switch, or reuse Git branches while normalizing the feature directory and ensuring spec.md exists. It outputs the final branch name, spec file, and feature directory for downstream steps.

Creating a feature branch for non-Git workspaces reuses or establishes the branch logic and normalizes the feature directory to changes/<dir>. It ensures spec.md exists and returns the branch name, spec file, and feature directory for subsequent workflow tasks.

Normalizing feature directory paths standardizes the location to changes/<dir> and verifies that spec.md is present. This process outputs the final branch name, spec file path, and normalized feature directory to support spec-driven development workflows.

Yes, creating a Git feature branch applies to both explicit inputs and inferred descriptions. It processes the provided context to decide the branch action, normalizes the feature directory, and outputs the branch name, spec file, and feature directory.

No, you do not need an existing Git repository as this process applies to both Git and non-Git workspaces. It decides the branch action, normalizes the feature directory, ensures spec.md exists, and outputs the branch name and file paths.

A spec-driven workflow requires a normalized changes directory and spec.md file to maintain consistent feature tracking. The process normalizes the directory to changes/<dir>, validates spec.md existence, and outputs these paths for downstream activation.