Parses new Gherkin scenarios produced by acceptance-criteria-extractor, fingerprints each scenario by its Given/When/Then step sequence, diffs the fingerprints against existing step-definition usage in the live suite, and emits a coverage/duplicate map showing which new scenarios are already covered, which overlap partially, and which are genuine gaps. Use when acceptance criteria have been converted to .feature files and before any new automated tests are authored.
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Deep reference for the gherkin-scenario-coverage-map skill - the full
markdown templates Step 5 emits. SKILL.md keeps the compact four-part
instruction; the filled-in shapes live here.
List each DUPLICATE scenario with the existing scenario it mirrors:
### Duplicates (do not author - already covered)
| New Scenario | Existing Scenario | File |
|---|---|---|
| "User logs in with valid credentials" | "User submits correct password" | `auth/login.feature:14` |For each PARTIAL scenario, list the new steps (steps not yet in the index)
and the existing steps (already covered):
### Partial overlaps (author only the new steps)
**Scenario: "Admin resets user password"**
- Already covered steps (3): step text A, step text B, step text C
- New steps required (1): "the user receives a password-reset email"
- Recommendation: add one new step definition; reuse existing definitions
for the 3 covered steps.List each GAP scenario in full, marked ready for new test authoring:
### Gaps (author full scenario)
- "Password reset rate-limits after 5 attempts" (0 of 4 steps covered)
- "SSO login redirects to IdP" (0 of 3 steps covered)## Coverage map for `<story-id>` (<date>)
**New scenarios evaluated:** N
**Exact duplicates:** A (skip these)
**Partial overlaps:** B (extend step definitions only)
**Genuine gaps:** C (author full scenarios)
**Step-usage index built from:** M existing .feature files / JSON report