plan

Create Plan: $ARGUMENTS

For universal orchestration discipline (background spawning, signal routing, reviewer gate semantics, auto-revise threshold, user touch points, drift detection), reference .claude/skills/orchestrate/SKILL.md — already loaded in your context when you reach this skill.

This skill is plan-specific. Don't duplicate universal patterns here; reference them.

Plan translates ticket's WHAT into sequenced HOW (files, names, ordering, criteria). Plan does NOT decide WHAT (brainstorm's job). Plan does NOT do the work (implementer's job). If planner finds itself making architectural calls, ticket was inadequate — route back upstream.

<check id="clarify-goal">
  If $ARGUMENTS is ambiguous, ask before spawning. Don't guess the end state.
  (This IS a legitimate touch point — architectural clarification, not workflow permission.)
</check>

<check id="find-parent-ticket">
  query({ "type": "ticket" }) or current project's ticket list.
  Pass ticket_id to planner so create_plan links under it.
</check>

<check id="pattern-context">
  assemble({ id: ticket_id }) — check ## Patterns section.
  If NEITHER pattern_ids NOR no_patterns_reason set, prompt user with options:
  (a) Run /brainstorm to pick patterns
  (b) Add no_patterns_reason via mutate (escape hatch for trivial work)
  (c) Cancel
  Do NOT auto-invoke /brainstorm — user picks.
</check>

<check id="ticket-thoroughness" severity="gate">
  Verify ticket has:
  - In Scope enumerating concrete code surfaces (files, packages, functions)
  - Out of Scope explicitly naming temptations + adjacent work deliberately excluded
  - Success criteria with testable invariants (named assertions; a criterion
    asserting a SHAPE in source belongs in a corpus check, which cannot be
    stored until it has fired on a bad fixture and stayed silent on a good one)

  If ticket is thin, STOP:
  "The ticket is too thin for direct planning — the architectural surface needs
  to be enumerated first. Run /brainstorm against the ticket to do the
  architectural walk + populate In Scope / Out of Scope concretely, then
  re-run /plan."

  Do NOT spawn planner against thin ticket.
</check>

See orchestrate constraint id="dispatch" — every spawn is background.