What problem does it solve? Requirements, bug reports, and PRDs often arrive as unstructured prose that implementing developers or autonomous agents cannot act on directly, causing work to bounce back for clarification. This Skill converts that raw material into structured, testable delivery tickets with explicit scope, dependencies, and verifiable Gherkin acceptance criteria. ## Core Features & Use Cases - Three operating modes: write a single ticket from one request, decompose a larger source (PRD, spec, epic) into a batch of dependency-ordered vertical slices, or produce a pasteable acceptance-criteria block for an existing ticket. - Gherkin acceptance criteria as contract: every ticket carries checklist-style Given/When/Then criteria that an independent reviewer or implementing agent can judge a diff against, with stable issue IDs and explicit dependency metadata. - Acceptance coverage gate: in pipeline batch mode, maps every PRD requirement obligation to a ticket or an explicit outstanding entry and validates the result with a read-only CLI gate before the issues phase completes. - Use Case: Given a gated prd.md and spec.md for a new feature, decompose them into a complete issues.md of tracer-bullet vertical slices — each with immutable IDs, requirement traceability, and testable acceptance criteria — ready for unattended agent implementation. ## Quick Start Ask the agent to decompose the feature's prd.md and spec.md into a batch of implementation-ready tickets with Gherkin acceptance criteria written to issues.md.
