What problem does it solve? Turning an approved specification into actionable work is error-prone: tickets end up oversized, dependencies are missed, and agents or developers start blocked because briefs lack scope, API shapes, or verification steps. This Skill converts a spec into an ordered backlog of right-sized tickets that can be executed sequentially without re-reading the entire spec. ## Core Features & Use Cases - Ticket decomposition with sizing: Splits a spec into vertical slices sized S/M/L, with a mandatory split plan for any L ticket touching unrelated subsystems. - Dependency mapping and ordering: Enforces the schema → domain → API → UI ordering rule, detects circular dependencies, and produces an execution-order table with labels. - Agent-ready briefs: Generates a self-contained markdown block per ticket covering objective, spec references, scope, test seams, verification commands, and definition of done. - Use Case: After approving a coupons feature spec, run this Skill to produce tickets T-101 (migration), T-102 (API), T-103 (UI) with dependencies, labels like migration and agent-ready, and paste-ready issue bodies. ## Quick Start Break the approved coupons spec into ordered, sized tickets with dependencies and agent-ready briefs for each one.
