/refine

/refine decomposes one oversized official item into autonomous child items. Direct invocation reads the complete item context, including comments, before assessing the need for decomposition. When called from /pick, it reuses the complete context and assessment returned by /plan. The parent stays unchanged, and no child is created before the human confirms the complete decomposition.

How /refine decomposes an item

01 · Standalone onlyComplete and assess contextRead the complete item context and confirm that multiple useful units exist. Caller mode reuses the assessment from /plan.

Refinement needed

02 · AssistedDraft child itemsCover the parent scope exactly once with vertical feature slices or a justified progressive sequence.

One delivery unit

OutcomeNo changesReport refinement-not-needed and stop.

↓

Validation loop

02 · SpecialistRevise decompositionKeep complete child proposals and genuine blocking relations.

03 · WorkflowValidate decompositionReturn every contract deficiency to the same specialist.

Fix deficiencies

Valid decomposition↓

Confirmation loop

04 · AssistedPreview all childrenShow complete bodies and blocking relations without creating them.

HumanReview decompositionConfirm everything, request an adjustment, or cancel.

Adjust decomposition

Confirm all children↓

05 · WorkflowCreate confirmed decompositionKeep feasible operations running, report successes and failures separately, and leave the parent unchanged.

Skills used under the hood

Assessmentplanning-and-task-breakdown ↗Check whether the selected item contains multiple useful units that can be delivered or verified separately.Decompositionto-tickets ↗Prefer vertical feature slices and allow justified expansion, migration, and removal sequences.

What /refine does

1	Assess	In standalone mode, read the complete context and stop without changes when the item is one indivisible delivery unit. Caller mode reuses the complete context and assessment from /plan.
2	Draft	Use one specialist to draft at least two useful children that cover the parent scope exactly once, preferring vertical feature slices and allowing justified progressive migrations.
3	Validate	Return every deficiency to the same specialist until the complete decomposition is valid.
4	Confirm	Preview every child and relation, then confirm everything, adjust the draft, or cancel without changes.
5	Create	Require creation prerequisites first, then create confirmed children in order, copy agent-shaped when required, persist valid blocking relations, continue feasible operations after individual failures, and report successful and failed results separately.