gherkin-scenario-reviewlisted

# Reviewing Gherkin ## Overview Reviewing a feature file is a different job from writing one. The text already exists, somebody meant it, and the useful output is not a verdict but a rewrite. A review that says "this is too imperative" helps nobody; a review that shows the same scenario four lines shorter and more truthful gets merged. This skill supplies the diagnosis and the repair for each recurring defect. ## When to use this skill - A pull request adds or changes `.feature` files. - Someone asks whether a scenario reads well. - A suite has become slow, flaky, or unreadable and nobody knows where to start. - Feature files arrive from another team and need assessing. - A refactor of existing scenarios is requested. If the scenarios do not exist yet, write them with the scenario-writing skill instead. If the underlying rules were never agreed, no amount of rewriting will fix the file, and the work belongs in discovery. ## How to review Read in three passes. Each pass finds a class of problem the others miss, and doing them at once produces a scattered review. 1. **Names only.** Read the feature name and every scenario name, in order, ignoring the steps. Does the list describe a capability? Could a reader spot a missing rule from the gaps? Most structural problems are visible here alone. 1. **Altitude.** Read the steps looking only for detail that has leaked down from behaviour into mechanism, and for scenarios that depend on each other. 1. **Truth.