Workflow

Explore the solution space after the problem is defined. Evaluate approaches, form project-specific principles, and pick a direction. Sits between problem definition and planning. Use when the problem is defined but the approach isn't decided yet.

Turn a defined problem and chosen direction into a concrete proposal. Two Codex agents propose independently, Opus synthesizes the best parts, user approves. Use after problem definition (and design, if applicable), before implementation.

Full bug-fix pipeline from root cause analysis through implementation. Separates investigation, proposal, alignment, and execution into distinct agent responsibilities. Also applies to features and refactors by skipping root cause analysis and starting at proposal.

Execute the approved proposal. Sub-agents build in parallel, each assigned a domain scope. Verification checks against the problem and principles, not the proposal document. Two-round iteration limit on failures. Use after planning has produced an approved proposal.

Frame and clarify problems before any planning or implementation begins. Use when starting new work, when requirements are unclear, or when the user describes what they want built. This is the first step — before planning, before code.