Feature Branch + PR Workflow

Overview

Use a consistent git workflow so every feature/change is done in a branch and submitted as a PR.

Workflow

1. Confirm PR Requirements

• Identify target branch (e.g., main or develop).
• Ask for branch naming rules if not specified.
• Confirm if a PR template, labels, or issue references are required.

2. Create Branch

• Create a new branch before modifying code.
• Auto-pick branch name using phase number + short feature name.
• Use format: phase-<number>-<short-name> (e.g., phase-5-1-scout-llm).
• If the phase has substeps (e.g., 5.1), include them (e.g., phase-5-1).