/plan

/plan turns one task into an approved implementation plan. It first checks that the task is one coherent delivery unit, routes the work to the right specialist, and resolves every material question before asking for approval. For an official item, it then publishes the approved plan in a dedicated comment and applies agent-planned. Before assessing an official item, it completes the supplied context with any missing labels, comments, linked resources, and attachments supported by the provider. On needs-refinement, it returns that complete context with its findings so /pick can pass them to /refine.

An explicit item ID, URL, or title is resolved as official item context. A direct invocation still uses plan-only approval: it may publish an official item plan, but it does not start delivery. When /plan is called by /pick, approval also authorizes autonomous delivery and returns control to /pick so it can continue with /work.

Each plan shows todo state beside its numbered step with one symbol: ○ for pending, ◐ for in_progress, ✓ for completed, and ⊘ for cancelled. /work updates the symbol, and /ready uses the step states when checking that delivery is complete.

How /plan reaches approval

01 · AssistedCheck delivery scopeDecide whether the task is one independently deliverable unit.

One delivery unit

02 · AssistedSelect a specialistInspect the relevant context and author the plan.

Multiple delivery units

Outcomeneeds-refinementReturn concise findings without creating a plan.

↓

Planning loop

03 · AssistedDraft or revise planKeep the fewest small, verifiable steps.

HumanAnswerResolve decisions that materially change the plan.

Material question

No open question↓

Approval loop

04 · AssistedPresent complete planShow every step, validation, and the delivery scope.

HumanReview planApprove the plan with the current entry mode’s scope or request an adjustment.

Adjust plan

Approve plan↓

OutcomeApproved planStandalone mode does not start delivery. Caller mode authorizes autonomous delivery through successful /inspect.

Skills used under the hood

Alwaysplanning-and-task-breakdown ↗Check delivery scope and structure the fewest verifiable steps.External facts mattersource-driven-development ↗Verify and cite a versioned fact that affects the plan.Decision is high-riskdoubt-driven-development ↗Challenge one unfamiliar or high-risk decision before approval.

What /plan does

1	Assess	Continue for one delivery unit or return needs-refinement through the active context branch without creating or publishing a plan.
2	Plan	Route to one specialist, inspect the relevant context, and write the plan.
3	Resolve	Ask and incorporate every answer that could materially change the plan.
4	Approve	Present the complete plan and revise it until the human approves it. Standalone approval completes only /plan; workflow approval returns to its caller with autonomous delivery authorized.
5	Publish	For an official item, publish the approved plan, require the mutation response to identify the created comment, then apply agent-planned. Stop before labeling when publication fails or is inconclusive.