ralplan

Coordinate multi-agent consensus planning to produce an approved executable plan.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/eszxcvfd/ANIZAKI --skill ralplan-eszxcvfd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/eszxcvfd/ANIZAKI/tree/main/.agents/skills/ralplan
Command: npx skills add https://github.com/eszxcvfd/ANIZAKI --skill ralplan-eszxcvfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan solves the problem of underspecified execution requests by routing them through a structured, multi-agent consensus planning workflow (Planner, Architect, Critic) to produce a clear, approved plan before execution.

Core Features & Use Cases

  • Orchestrates a three-phase planning loop (Planner → Architect → Critic) to generate comprehensive plans.
  • Supports interactive and non-interactive modes with explicit gatekeeping and approval steps.
  • Produces an ADR-style final plan with decisions, drivers, and acceptance criteria for safe execution.

Quick Start

Plan a new feature rollout for the billing module using consensus planning.

Frequently Asked Questions about ralplan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is multi-agent consensus planning for software development?

Multi-agent consensus planning coordinates Planner, Architect, and Critic agents to evaluate complex requests and produce an executable plan. This governance workflow ensures explicit acceptance criteria and team scope alignment.

How do I create an executable plan for complex deployment tasks?

To create an executable plan, route your complex deployment task through interactive or automated planning rounds. The workflow applies formal gatekeeping to produce an ADR-style output with defined decisions and acceptance criteria.

Can I run automated planning workflows without manual intervention?

Yes, you can use non-interactive modes to run automated multi-agent planning. The workflow executes Planner, Architect, and Critic rounds with formal gatekeeping to deliver approved plans without continuous manual intervention.

Does multi-agent planning work for both interactive and automated governance?

Yes, the consensus workflow supports both interactive and automated governance modes. It applies formal gatekeeping and approval steps during the planning loop to align teams and bound the execution scope.

Why do I need consensus planning for underspecified execution requests?

You need consensus planning to prevent unbounded execution of underspecified requests. It routes tasks through a three-phase planning loop to produce an ADR-style output, ensuring all architecture decisions and acceptance criteria are formally approved.

What are the limitations of using a three-phase planning loop for workflow governance?

A limitation of the three-phase planning loop is the overhead required for formal Planner, Architect, and Critic rounds. It is built for complex development governance and may be excessive for simple execution requests lacking scope constraints.