skills.rest
shayne-snap
shayne-snapCOMMUNITY
Explore all skills by this author →
Website𝕏@shayne_snapeGitHub

ralplan

Generate consensus-based product and execution plans with PRD and test-spec artifacts.

3|Updated May 24, 2026
Search Tags:#planning#risk management#consensus#ADR#software workflow#test specification#runtime handoff
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill ralplan-shayne-snap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/ralplan
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill ralplan-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan prevents you from rushing into implementation by driving structured, iterative planning until multiple planning roles reach consensus.

Core Features & Use Cases

  • Consensus-driven planning: Runs planning with Planner, Architect, and Critic roles until consensus is reached using RALPLAN-DR deliberation.
  • Deliberate-mode safety planning: Optionally expands safeguards for auth/security, migrations, destructive changes, production incidents, compliance/PII, or public API breakage.
  • Artifacts + gated handoff: Produces matching PRD and test-spec files under .omagy/plans and forces a closed-fail requirement so execution cannot start without both.
  • Execution-ready handoff: Completes runtime state and generates verified launch hints for team execution via /omagy:team or single-owner execution via /omagy:ralph.

Quick Start

Run Ralplan with consensus planning for the task you want to implement so the workflow generates the PRD and test spec and prepares a safe handoff.

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I create a consensus-based execution plan before starting software implementation?▼

Consensus-based execution planning is generated by running iterative planning sessions across Planner, Architect, and Critic roles until agreement is reached, preventing premature implementation through a gated handoff.

What is deliberate-mode safety planning for high-risk software changes?▼

Deliberate-mode safety planning expands safeguards for high-risk changes involving auth, security, migrations, destructive actions, production incidents, compliance, PII, or public API breakage during the consensus workflow.

How do I gate code execution until a PRD and test specification are approved?▼

Execution is gated by enforcing a closed-fail requirement that blocks runtime handoff until both matching PRD and test-spec files exist under the plans directory, ensuring verified artifacts precede implementation.

Does consensus-driven software workflow planning work for both team and single-owner execution?▼

Consensus-driven planning supports both paths by completing runtime state and generating verified launch hints for team execution or single-owner execution after the approved handoff is reached.

When do I need risk management and architectural review before implementing a software feature?▼

Risk management and architectural review are needed before implementation when changes involve destructive actions, security modifications, or public API breakage, requiring deliberate-mode safeguards and Critic role validation.

Related Skills

Explore More Software Engineering Skills→
JaCha00JaCha00

ralplan

Coordinate Planner, Architect, and Critic agents for consensus-driven task planning.

Community
Advanced
ilandahanilandahan
9

aid-impl-plan

Consolidate Phase 1 PRD and Phase 2 Tech Spec into a unified Phase 3 plan.

Community
Advanced
marlandojmarlandoj
23

three-stage-eval

Evaluate artifacts against seed specifications with mechanical, semantic, and consensus checks.

Community
Advanced
ozbyozby
1

ralplan

Coordinate multi-agent planning with Planner, Architect, and Critic roles to produce a consensus plan.

Community
Advanced