What problem does it solve? Teams using spec-kit workflows need feature branches to follow strict naming conventions so that specs, branches, and directories stay linked. Manually checking branch names is error-prone, and working on a misnamed branch can break downstream spec tooling. ## Core Features & Use Cases - Branch Name Validation: Checks the current Git branch against sequential patterns (e.g., 001-feature-name) and timestamp patterns (e.g., 20260319-143022-feature-name). - Spec Directory Detection: Verifies that a matching spec directory exists under specs/ for the branch prefix. - Graceful Degradation: Falls back to the SPECIFY_FEATURE environment variable when Git is unavailable, and skips validation with a warning instead of failing. - Use Case: Before running spec-kit commands like plan or implement, validate that you are on a properly named feature branch so generated artifacts land in the correct spec directory. ## Quick Start Ask the assistant to validate that the current Git branch follows the spec-kit feature branch naming convention.
