gherkin-suite-designlisted

# Designing a specification suite ## Overview Individual scenarios can all be good while the suite is unusable. Suites fail at the level above the scenario: files organised by screen, tags that mean four things, a run nobody waits for, and documentation nobody reads because it was never published anywhere. This skill is about that level. ## When to use this skill - Starting a suite in a new or existing codebase. - Deciding how to divide behaviour across feature files. - Designing or repairing a tagging scheme. - Publishing scenarios so people outside the delivery team see them. - Wiring the suite into continuous integration and deciding what runs when. - The whole run has become too slow or too distrusted to be useful. For phrasing one scenario, use the scenario-writing skill. For critiquing existing files, use the review skill. For the code behind the steps, use the automation skill. ## Organise by capability The organising unit is a capability the business would name, not a screen, a controller, or a sprint. ```text features/ lending/ borrowing-limits.feature late-fees.feature renewals.feature reservations/ placing-a-reservation.feature collecting-a-reservation.feature membership/ registration.feature tiers.feature ``` Screens get merged and redesigned; capabilities persist. A folder named `member-page` will be wrong within a year, and nobody will know which of its scenarios to move. Two practical rules. Name files after the ca