ralplan

To build a consensus plan from ambiguous requests, this Skill uses an iterative Planner, Architect, and Critic loop to refine scope and generate explicit acceptance criteria. It ensures alignment by producing a final ADR covering decisions, drivers, alternatives, and consequences.

Documenting architecture trade-offs is handled through automatic ADR generation, capturing the decision, drivers, alternatives, why it was chosen, and consequences. This explicit decision framing ensures stakeholders understand the rationale behind architectural choices before execution.

Yes, high-risk software projects can use the deliberate mode to add risk pre-mortem scenarios and expanded test planning. This injects additional safety analysis into the consensus loop, ensuring potential failure modes are evaluated before final user approval.

The iterative critique loop works by generating an initial project rollout strategy, then applying architectural review and critique across up to five iterations. The plan is repeatedly refined against quality gates until a testable consensus is reached for final user approval.

Yes, execution gating is a core feature that redirects vague execution requests into a structured scoping and validation workflow. This prevents under-scoped work by enforcing explicit acceptance criteria and requiring final user approval before any execution begins.

A multi-agent consensus loop is needed for software and product planning when requests are vague and involve complex architectural trade-offs. It ensures quality gates and approval workflows are met through Planner, Architect, and Critic interactions before execution.