/refine

/refine splits one oversized official item into confirmed child items. Start it directly by selecting an item, or enter from another workflow after /plan returns needs-refinement.

Dispatching external skills

/refine uses one Skill to confirm the scope when it starts standalone and a second Skill to produce vertical child tickets. The local workflow keeps control of provider access, presentation, approval, child creation, and blocking relations.

Workflow/refineOwns context, approval, and provider mutations

↓SkillStandalone only: confirm that refinement is neededplanning-and-task-breakdown ↗Addy Osmani↓SkillDraft vertical child tickets and genuine blocking edgesto-tickets ↗Matt Pocock

How this workflow is structured

1	Context	Reuse the caller’s official item or select and read one in standalone mode.
2	Scope	In standalone mode, confirm that the item contains multiple autonomous delivery units.
3	Decompose	Draft vertical child tickets and identify only the dependencies that genuinely block them.
4	Revise	Check that the decomposition is complete and non-overlapping, then return it to the same specialist when corrections are needed.
5	Review	Preview the complete decomposition, then confirm, adjust, or cancel it.
6	Create	Create every confirmed proposal as a native child and persist its blocking relations.
7	Stop	Report every created child and blocking relation or any partial failure without changing the parent.