review-feature-suitelisted

# Review Feature Suite A single `.feature` file can be flawless on its own and still be wrong in the company of its neighbors. The value of a BDD suite is that the whole team shares one language all the way down into the code, that step definitions are written once and reused, and that the features stand as living documentation that doesn't contradict itself. Those properties only exist *across* files, so they can only be checked across files. That is this skill's entire job: read every `.feature` file as one corpus and reconcile it. Work in two phases: **critique first, edit second.** Build the picture, surface the findings, settle the judgment calls with the user, and only then change files. ## Build the inventory first The findings live in the relationships between files, so don't read file-by-file and judge as you go — assemble a compact cross-file picture first, then reason over it. Use `Glob` to enumerate the `.feature` files from the path or glob the user gave (default to searching the project), then use `Grep` to pull the raw material across all of them at once rather than holding every full file in context: - **Steps** — every `Given`/`When`/`Then`/`And`/`But` line, so you can see which phrasings recur and which are near-duplicates. - **Tags** — every `@tag`, to spot the taxonomy and its typos. - **Titles** — every `Feature:` and `Scenario:`/`Scenario Outline:` line. - **Actors and data** — the roles, currency/number/date values, and named entities that recur, s