ralplan

Orchestrate Planner, Architect, and Critic cycles to produce a consensus work plan.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/suhwan/claude-registry --skill ralplan-suhwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/suhwan/claude-registry/tree/main/skills/project/ralplan
Command: npx skills add https://github.com/suhwan/claude-registry --skill ralplan-suhwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This multi-agent planning workflow coordinates Planner, Architect, and Critic to converge on a complete, consensus-based work plan, reducing ambiguity and rework.

Core Features & Use Cases

  • Orchestrates iterative cycles among Planner, Architect, and Critic to reach a final, validated plan.
  • Applies to complex projects requiring architecture review, cross-functional validation, and quality safeguards.
  • Use Case: plan a feature with architectural questions and multiple reviews until a consensus plan is approved.

Quick Start

Provide a task to ralplan and let Planner-Architect-Critic iterate until a consensus plan is produced.

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I coordinate multi-role planning to reach a consensus work plan for complex projects?

Iterative planning applies up to five cycles involving a Planner, Architect, and Critic to validate architecture decisions. It is needed when complex projects require cross-functional reviews and multiple approvals to converge on a final work plan.

What is the best way to orchestrate iterative project management cycles with cross-functional reviews?

The best way to orchestrate iterative project management is using a multi-agent workflow that iterates up to five cycles. This approach applies architecture review and quality safeguards until a consensus plan is approved, reducing rework.

Can I use a Planner-Architect-Critic workflow for complex projects with architecture decisions?

Yes, the Planner-Architect-Critic workflow is designed for complex projects with architecture decisions. It iteratively refines the plan through cross-functional validation and quality safeguards until final approval is reached.

How many iterative cycles does consensus planning run before finalizing a work plan?

Consensus planning runs up to five iterative cycles with the Planner, Architect, and Critic. The process continues refining the work plan through cross-functional reviews until approval is reached and a validated plan is produced.

When should I not use iterative multi-agent planning for project management?

Iterative multi-agent planning should not be used for simple tasks lacking architectural questions or cross-functional review needs. It is designed for complex projects requiring multiple reviews and consensus building to reduce ambiguity and rework.