ralplan

Coordinate Planner, Architect, and Critic roles to produce a validated plan.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill ralplan-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_codex/skills/ralplan
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill ralplan-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan accelerates and standardizes planning by orchestrating Planner, Architect, and Critic roles to produce a validated, consensus-driven plan.

Core Features & Use Cases

  • Orchestrates a multi-agent planning loop (Planner → Architect → Critic) to ensure thorough review and high-quality plans.
  • Supports both automated and interactive consensus flows, including pre-mortem and expanded test planning in deliberate mode.
  • Produces decision records, alternatives considered, and actionable steps ready for execution.

Quick Start

Provide a clear task description to begin a ralplan consensus planning session.

Frequently Asked Questions about ralplan

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

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

Consensus-driven planning coordinates Planner, Architect, and Critic roles to produce a validated plan. It is designed for underspecified requests and high-risk tasks where explicit scope and test criteria are required before execution.

How do I create an architecture decision record for a high-risk task?

You can create an architecture decision record by initiating a consensus-driven planning workflow that enforces an iterative review loop and automatically documents decision records, alternatives considered, and actionable steps for traceability.

Can I automate the planning loop for underspecified project requests?

Yes, consensus planning supports both automated and interactive flows. The multi-agent loop orchestrates Planner, Architect, and Critic roles to systematically expand scope and generate pre-mortem and test plans in deliberate mode.

When should I use a multi-agent consensus workflow over standard planning?

You should use a multi-agent consensus workflow for high-risk tasks and underspecified requests where explicit scope and test criteria are required. The Planner, Architect, and Critic loop ensures thorough review before execution.

Does consensus planning require external dependencies to run the iterative review?

No external dependencies are required to run the iterative review loop. The consensus-driven planning workflow operates independently to coordinate the Planner, Architect, and Critic roles and produce validated plans.