Step 2: Plan

RULES

• No human interaction: do not ask questions or wait for approval in this step.

INSTRUCTIONS

1. Draft resume check. If {plan_file} exists with status: draft, read it and capture the verbatim <intent-contract>...</intent-contract> block as preserved_intent_contract. Otherwise preserved_intent_contract is empty.
2. Investigate codebase. Read the code yourself for narrow, localized tasks. Isolate deep exploration in synchronous subagents: instruct them to give you distilled summaries only, and plan from those summaries. Decide which findings actually matter for execution — the specific files, symbols/lines, reuse points, and read-only constraints — and carry those forward for the Code Map. This is where the investigation lands: the plan preserves it so it is never re-narrated to the implementer at dispatch time.

Treat a codebase research document as evidence for this investigation, read at its commit. Before the plan uses a claim from it, re-check it against the current code when the plan rests on it or its cited file changed since that commit (git diff --stat <commit> -- <path>). Investigate afresh any claim that no longer holds.

Then score the change's risk for {plan_file} frontmatter: low, medium, or high, the business impact if this change is wrong. For a ticket from the tree, start from risk in tickets.py find's output and raise it when the investigation shows more; never go below it. {% if workflow.route == "oneshot" or workflow.route == "full" %}

1. The route is {{ workflow.route }}; route_source is pinned.

{% else %}

1. {{ workflow.route_selection }}

route_source is auto. {% endif %}

1. Read {{ rendered("plan-template.md") }} fully, preserving all frontmatter fields and resolving date to the current system date.
2. Oneshot: set route: 'oneshot'.
3. Full: set route: 'full'. Put what you learned into ## Code Map: paths, symbols or lines, what to reuse, and what not to change. The subagent should be able to work from the plan without being told any of it again.

Set route_source from step 3 and risk from step 2.

If {preserved_intent_contract} is non-empty, substitute it for the <intent-contract> block before writing {plan_file}. Self-check against the route's READY FOR DEVELOPMENT standard.

1. If intent gaps exist, do not fantasize and do not leave open questions. Multiple defensible readings of the intent that lead to observably different outcomes, with nothing in the intent to select between them, are an intent gap — do not resolve one by picking a reading. HALT with status blocked, blocking condition intent gap, and include the unanswered questions and evidence gathered.
2. Warning check. If step-01 carried multiple-goals, add it to {plan_file} frontmatter warnings. If {plan_file} exceeds 1600 tokens, add oversized to frontmatter warnings. Continue either way.

READY-FOR-DEVELOPMENT GATE

Re-read {{ rendered("workflow.md") }}, then re-read {plan_file} from disk and verify the plan meets the READY FOR DEVELOPMENT standard.

• If the file is missing: HALT with status blocked and blocking condition plan file disappeared before implementation.
• If the plan meets the standard: set {plan_file} frontmatter status to ready-for-dev. If the invocation prompt directs a halt after planning (standard phrasing: Halt after planning. — accept any clear equivalent), HALT with status ready-for-dev; otherwise continue to step 3.
• If the plan does not meet the standard: repair it once, then re-read it from disk and verify again. If it now meets the standard, apply the If the plan meets the standard handling above, including the halt-after-planning check. If it still does not meet the standard, HALT with status blocked, blocking condition plan failed ready-for-development standard, and include the failing criteria and evidence gathered.

NEXT

Read fully and follow {{ rendered("step-03-implement.md") }}