What problem does it solve? When turning an interviewed feature request into tickets, it is hard to decide whether the work should stay as a single ticket or be split into an Epic with phased, dependent tasks. This Skill applies consistent structural heuristics to make that call and produce a ready-to-use creation plan. ## Core Features & Use Cases - Single vs. mission decision: Returns a discriminated-union result (single or mission) based on deliverable count, blocking dependencies, file scope, and domain spread. - Structural tagging: Populates Epic, Phase, Step, and DependsOn fields only when the mission genuinely warrants them, omitting fields that do not apply. - Self-contained task bodies: Carves Requirements and Acceptance Criteria per task, copies Context and Source to every task, and distributes Open Questions to the tasks they affect. - Use Case: After /notion-dev:ticket-interviewer drafts a request like "Add Litecoin support", the Skill returns a mission with an Epic name and four phased tasks with explicit dependencies, which /notion-dev:create-task then creates. ## Quick Start Ask the assistant to run task-breakdown on the drafted ticket from the interviewer to decide whether it should be one ticket or a multi-task mission.
