work-plan

Work / 3. Plan

Produce an implementation-ready plan without changing source files.

Make the plan protect reliability, restraint, modular boundaries, the simplest complete implementation, human authorship, clean breaks over obsolete compatibility, meaningful tests, and proof over status reports. Prefer existing dependencies and durable architecture over speculative packages or stopgaps.

Fixed route

• If the exact subagent model, effort, or goal tools are unavailable, return blocked with the missing capability. Do not substitute a model or perform the analyst's work in the parent.
• Launch exactly one gpt-5.6-sol subagent at xhigh effort with fork_turns: none.
• Give it a fun call sign, the exact task statement, source of truth, read-only ownership, constraints, acceptance checks, and validation requirements.
• Require it to inspect independently and return concrete evidence, not a status report or a claim that an unproved step is “routine.”
• Require it to call create_goal with the exact analysis goal before inspection and update_goal complete only after the required evidence is collected.
• Let the analyst run until it returns the plan, a real blocker, or a user-input request. Do not cancel it because a polling window or arbitrary wall-clock interval elapsed; a wait timeout is not a failure.
• The analyst must not edit, commit, deploy, spawn, or delegate.
• Scale depth to the task. Inspect only relevant paths, direct consumers, and evidence needed for the handoff; return the plan without process narration and stop when every required field is supported.
• Report the successful launch as a compact table with Agent, Working on, Goal, Ownership, and Model.

Build the plan

The parent defines the mission. The analyst inspects only relevant context, traces current behavior through real consumers, and resolves evidence-backed decisions. Keep early alternatives independent; do not let the first elegant reduction become the plan without checking it against the exact task. The parent verifies paths, symbols, commands, and assumptions before returning the handoff.