Concepts (ISTQB definition, Gherkin reference) are linked out rather than re-explained, and the prose stays procedural; every section (steps, output format, anti-patterns) earns its place.

Provides concrete, executable Gherkin templates with real data-testid selectors, HTTP status codes, and Examples tables, plus a copy-paste output-format template.

Steps 1–6 are clearly sequenced, with Step 4 as an explicit validation gate (reject unobservable Thens) and Step 6 as a flag-and-ask quality gate; the destructive/batch feedback-loop cap does not apply to this generation task.

Core procedure stays inline while worked examples are correctly split to the real references/examples.md, a clearly signaled one-level-deep reference (verified to exist).

"emits well-formed acceptance criteria as Given/When/Then steps in Gherkin... or as a numbered plain-text list. Identifies missing-precondition gaps and proposes Background blocks" lists multiple specific concrete actions.

Clearly answers both what (emit AC in two shapes, identify gaps, propose Background) and when ("Use after a story is testability-confirmed and before implementation begins"), satisfying the explicit-trigger requirement.

Contains natural domain terms a user would say ("user story", "PRD section", "acceptance criteria", "Given/When/Then", "Gherkin") with good coverage and no jargon-only gaps.

A clear BDD/acceptance-criteria niche with distinct triggers; the body further carves out non-functional requirements as out of scope, reducing conflict risk.