Generate consensus.md plans via a Planner, Architect, and Critic loop.
npx skills add https://github.com/Jurel89/copilot-omni --skill ralplan-jurel89
Please help me install this Agent Skill. Skill: ralplan Source: https://github.com/Jurel89/copilot-omni/tree/main/skills/ralplan Command: npx skills add https://github.com/Jurel89/copilot-omni --skill ralplan-jurel89
Ralplan addresses the issue of inefficient execution of vague requests by ensuring that explicit scope, testable acceptance criteria, and Planner/Architect/Critic consensus are established before code is written.
consensus.md plan artifact for downstream execution modes.To initiate planning, use the command: ralplan "My task description or spec"
High-intent search queries and answers about installing and using this skill.
A consensus loop handles underspecified requests by cycling a Planner, Architect, and Critic until approval or three cycles elapse, generating a consensus.md artifact with explicit scope and testable criteria for execution.
Intercepting underspecified requests before execution requires a pre-execution gate that drives a Planner, Architect, and Critic consensus loop, producing a consensus.md artifact defining explicit scope and testable criteria.
Yes, consensus planning generates testable acceptance criteria by driving a Planner, Architect, and Critic loop until approved, ensuring explicit scope is defined before execution.
The consensus loop processes tasks sequentially through Planner, Architect, and Critic roles, iterating until the Critic returns APPROVE or three cycles elapse, then generating a consensus.md plan artifact for execution.
Yes, downstream execution modes require the consensus.md artifact generated by the consensus loop, as it captures the explicit scope and testable acceptance criteria needed for structured code execution.
luqmannurhakimbazmanGenerate SPEC.md and PLAN.md for autonomous coding iterations with Claude.
phraExecute work items through autopilot, confirm, and validate modes.
solitude6060Convert underspecified execution requests into consensus-based plans via Planner, Architect, and Critic.
cellarwoodDraft product requirement documents with scope, acceptance criteria, dependencies, and launch gates.