What problem does it solve? Turning a finished product map into an actionable backlog is error-prone: tickets get cut from decisions instead of scope, dependencies go unrecorded, and issues are filed before anyone approves the plan. This Skill enforces a disciplined seven-step process that produces one ticket per capability, each traced to the smallest-version sentence. ## Core Features & Use Cases - Unit cutting from the smallest version: Derives each work unit from the one-sentence smallest version, forbidding plumbing-only tickets and decision-derived tickets. - Dependency ordering and tracing: Records real dependencies as needs #… lines and traces every unit back to a phrase in the smallest version, flagging untraceable scope. - Approval-gated tracker creation: Renders the full backlog as a board for human approval before creating all tickets at once via tracker-agnostic verbs, then generates a dependency graph. - Use Case: After charting closes a map for a habit-tracker app and the repo is scaffolded, run this Skill to produce four ordered, constraint-carrying tickets and hand the first one to /start-ticket. ## Quick Start Ask the assistant to cut the closed charting map into a backlog of tickets and show the board for approval before creating anything in the tracker.
