ralplan

Consensus-based planning is a structured workflow where Planner, Architect, and Critic agents iteratively generate, review, and refine project plans until agreement is reached, ensuring clear scope and test criteria before any code changes are made.

You can enforce a planning phase by running a consensus planning command with interactive and deliberate modes, which automatically redirects underspecified execution requests through pre-context intake and adds extra safety checks before development begins.

You need an iterative Planner-Architect-Critic loop for high-risk or multi-step projects requiring coordinated planning, multi-team coordination, and detailed testable plans, refining plans through up to five iteration cycles until consensus is reached.

Yes, interactive mode allows user prompts for review during the consensus planning workflow, enabling you to guide the iterative refinement process and ensure the generated plan meets your specific requirements before execution gating.

The best way to prevent vague execution requests from consuming resources is enforcing a structured planning phase that automatically gathers task context and redirects underspecified requests through consensus planning before any code changes are made.

The consensus planning workflow handles up to five iteration cycles for the Planner-Architect-Critic loop, meaning highly complex projects requiring extensive refinement beyond this limit may need manual intervention or additional planning phases to reach full agreement.