What problem does it solve? Go test code often drifts into inconsistent shapes across packages: split test functions, missing case identifiers, boolean error checks, and ad-hoc setup helpers. This Skill enforces one uniform test shape across all layers so any test reads the same way and stays traceable to BDD specifications in design documents. ## Core Features & Use Cases - Uniform test structure: One test function per method or function, external {pkg}_test packages, anonymous-struct table-driven tests, and a single execution/verification loop. - BDD traceability: Copies document BDD IDs, headings, and gherkin blocks verbatim into id / name / description fields, with untested BDDs listed as trailing comments. - Mechanical verification: Ships scripts/check-cases.py to validate package naming, unique IDs and names, and gherkin structure, alongside go vet and go test -shuffle=on. - Use Case: Given a domain-model document with BDD-014 scenarios, write a repository or usecase test where each case carries the document's ID and gherkin, then run the checker to confirm structural compliance. ## Quick Start Write tests for this Go method following the test convention, mapping each BDD scenario from the attached design document into table cases.