Git Branch or Naming Convention Awareness #7
Description
Summary
Define optional inference of role/phase from branch naming conventions.
Motivation
Branch names often imply work type; leveraging them improves relevance.
Proposed Approach
- Provide a mapping table (feature/* → Implementation).
- Require explicit confirmation before switching.
- Make it optional and project-specific.
Acceptance Criteria
- Spec section includes mapping examples.
- Clear confirmation requirement.
- Templates and prompt workflows updated to reflect spec changes, with validation passing.