gherkinlisted

> **Opt-in stage.** Acceptance tests (Gherkin + Reqnroll) are optional until introduced project-wide. Run this only when the user asks for acceptance coverage; otherwise skip straight from human gate 1 to `/implement`. See the Acceptance-tests policy in `.cursor/rules/agent-pipeline.mdc`. ## User Input ```text $ARGUMENTS ``` ## Prerequisites - Human gate 1 passed (`spec.md`, `plan.md`, `tasks.md` reviewed) - Run from the repository root Resolve feature directory: 1. Run `.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks` and parse `FEATURE_DIR` 2. If that fails, use `$ARGUMENTS` as feature path or `specs/` subdirectory ## Goal Emit executable Gherkin specifications only — no step definitions, no production code. ## Inputs Read from `FEATURE_DIR`: - `spec.md` — user stories, acceptance scenarios (Given/When/Then) - `tasks.md` — task IDs, user story phases (P1, P2, …) ## Output Create or update `FEATURE_DIR/acceptance/<story-slug>.feature`: - One file per user story (P1, P2, P3, …) - File name: kebab-case from story title (e.g. `trace-workbook-upload.feature`) ## Generation Rules 1. **Feature header:** `Feature:` line matches user story title; add `@P1` / `@P2` tag from priority 2. **Scenarios:** Convert acceptance criteria from `spec.md`; merge duplicates across criteria 3. **Prune:** - Drop implementation detail (class names, SDK types, connection strings) - Keep domain language (upload, queue, trace, tracking identifi