What problem does it solve? Turning a plan or Spec into actionable work items is error-prone: slices end up too coarse, horizontally layered, or entangled in merge conflicts. This Skill converts a plan into independently-grabbable, tracer-bullet Tickets on the project issue tracker with correct dependency edges and triage labels. ## Core Features & Use Cases - Vertical-slice breakdown: Splits work into end-to-end slices that each merge green on their own, with AFK (agent-mergeable) vs HITL (human-decision) routing classes. - Dependency management: Detects file-entangled slices and serializes them with req:N edges, publishes native blocked-by and sub-issue relationships, and inherits territory tags from the parent Spec. - Gated publishing: Requires explicit user approval of the breakdown and verifies referenced .red/ docs are landed on origin/{base} before creating any issues. - Use Case: After drafting an implementation plan for a new feature, run this Skill to quiz yourself on the slice granularity, then publish a dependency-ordered set of Tickets that an AFK agent fleet can drain in parallel. ## Quick Start Ask the agent to break the current plan or Spec into Tickets using the to-tickets skill, optionally passing tags like --tags backend,api.
