What problem does it solve? Teams using spec-kit workflows need feature branches to follow strict naming conventions so that specs, plans, and tasks stay traceable to the right branch. Manually checking branch names is error-prone, and working on a misnamed branch silently breaks the link between code and its specification directory. ## Core Features & Use Cases - Branch Name Validation: Checks the current Git branch against two accepted patterns: sequential prefixes like 001-feature-name and timestamp prefixes like 20260319-143022-feature-name. - Spec Directory Detection: Verifies that a matching directory exists under specs/ for the branch prefix, warning when the spec folder is missing. - Graceful Degradation: Falls back to the SPECIFY_FEATURE environment variable when Git is unavailable, or skips validation with a warning instead of failing. - Use Case: Before starting implementation on a spec-kit project, run this validation to confirm you are on branch 042-fix-login-bug and that specs/042-fix-login-bug/ exists, catching setup mistakes before any code is written. ## Quick Start Ask the assistant to validate that the current Git branch follows the spec-kit feature branch naming conventions and that its spec directory exists.
