ralplan

Consensus-driven planning transforms vague development requests into approved plans by running sequential Planner, Architect, and Critic passes to clarify scope and gate execution. It captures pre-context and documents tradeoffs until alignment is reached.

Execution gating redirects vague execution requests into planning first, preventing premature implementation. You need it for agent workflows requiring scope clarification, architectural critique, and interactive approval before starting sequential or parallel execution paths.

You add architectural review by applying sequential Planner, Architect, and Critic passes to your task planning. This consensus loop runs until the plan is approved or the iteration limit is reached, ensuring architectural critique is addressed.

Consensus planning preserves clear requests that already include concrete anchors such as files, tests, or issues. Execution gating specifically targets underspecified requests, redirecting only vague tasks into the planning workflow first.

A limitation of the Planner, Architect, and Critic review loop is the iteration limit; if consensus is not reached within the maximum iterations, the planning sequence stops. It also requires interactive approval handling before execution can proceed.