ralplan

Convert ambiguous engineering requests into consensus-driven ADR-backed execution plans.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/xz1220/oh-my-kimi --skill ralplan-xz1220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/xz1220/oh-my-kimi/tree/main/skills/ralplan
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill ralplan-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan solves the problem of turning an underspecified task request into a safe, testable execution plan by forcing a structured consensus among Planner, Architect, and Critic before any implementation happens.

Core Features & Use Cases

  • Consensus-style planning alias: Runs $plan --consensus flow to generate an ADR-backed plan instead of a single-shot outline.
  • Risk-aware modes: Supports automatic deliberate planning for risky requests and an explicit --deliberate flag that adds pre-mortem and expanded test planning.
  • Optional interactive approvals: With --interactive, it pauses at review/approval points to collect user decisions (proceed, request changes, reject) and then routes to execution (ralph/team/goal-mode) without directly implementing inside the planning skill.

Use it when you need a robust plan for engineering work, especially when scope, acceptance criteria, or risk level is unclear, such as refactors, migrations, security-related changes, or production-impact tasks.

Quick Start

Run: $ralplan "task description"

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I generate an ADR-backed execution plan from an ambiguous engineering task?

Consensus-driven planning converts ambiguous engineering task requests into an ADR-backed execution plan by forcing structured agreement among Planner, Architect, and Critic iterations before any implementation happens.

What is the best way to plan high-risk engineering refactors with pre-mortem analysis?

The best way to plan high-risk engineering refactors with pre-mortem analysis is using a deliberate planning mode that adds pre-mortem evaluations and expanded test planning to safeguard risky production-impact tasks.

How do I add interactive approval gates to an agent workflow execution plan?

You add interactive approval gates to an agent workflow execution plan by using an interactive review flag that pauses the process at review points to collect user decisions like proceed, request changes, or reject before routing to execution.

Does consensus planning support sequential step ordering for complex migrations?

Consensus planning supports sequential step ordering for complex migrations by converting underspecified scope and acceptance criteria into deliberate, testable execution steps without jumping straight into code implementation.

When should I not use a single-shot outline for engineering execution guardrails?

You should not use a single-shot outline when a task involves security-related changes or unclear risk levels, requiring deliberate-mode pre-mortem analysis and expanded test planning to safely establish engineering execution guardrails.