ralplan

Consensus planning works by orchestrating a Planner, Architect, and Critic to iterate on high-level objectives until they produce a final, approved plan with explicit context intake, risk assessment, and trade-off analysis.

To convert vague prompts into concrete plans, you submit high-level objectives to trigger a gated execution process that captures context, applies risk analysis, and outputs an ADR-backed plan with acceptance criteria and staffing guidance.

The best way to perform risk analysis and task scoping is by running a multi-agent coordination loop where a Critic validates an Architect's design against the initial plan until a testable, ready-to-execute consensus is reached.

Yes, explicit context intake is required for consensus planning because it gates execution, ensuring the final plan includes architectural decision records, drivers, alternatives, and test criteria before any task proceeds.

Yes, you can use multi-agent coordination to generate ADR-backed plans with acceptance criteria by having the Architect strengthen the Planner's initial design and the Critic validate quality through iteration loops until approval.