ralplan

Coordinate role-based planning and review workflows for complex software tasks.

10|Updated May 9, 2026

Search Tags:#workflow #planning #architecture #code review #risk management #claude-code

Ready to run

npx skills add https://github.com/jcwleo/oh-no-harness --skill ralplan-jcwleo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/jcwleo/oh-no-harness/tree/main/plugins/oh-no-harness/skills-claude/ralplan
Command: npx skills add https://github.com/jcwleo/oh-no-harness --skill ralplan-jcwleo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of vague, high-risk, or multi-step coding tasks by enforcing a rigorous, role-based planning and review workflow that ensures requirements are clear and strategies are vetted before implementation begins.

Core Features & Use Cases

Role-Based Workflow: Coordinates sequential handoffs between Analyst, Planner, and Plan-Reviewer roles to ensure architectural integrity and quality.
Risk-Aware Planning: Automatically selects planning depth (Light, Standard, or Thorough) based on the semantic risk of the task.
Use Case: Use this when you have a complex, cross-file refactoring project that requires a verified plan, architectural review, and a clear execution profile before any production code is touched.

Quick Start

Invoke the ralplan skill with a description of your complex task to initiate the planning and review process.

Frequently Asked Questions about ralplan

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

FAQPage Schema

How do I plan a complex software refactoring project before writing code?▼

Structured planning for complex software refactoring involves sequential role-based handoffs between Analyst, Planner, and Plan-Reviewer to vet architectural strategies before implementation begins. This approach ensures requirements are clear and risks are mitigated prior to touching production code.

What is the best way to manage architectural risk in multi-step coding tasks?▼

Risk management in multi-step coding tasks is handled through risk-aware planning that automatically selects planning depth—Light, Standard, or Thorough—based on the semantic risk of the task. This ensures high-risk, architecture-sensitive projects receive rigorous verification.

Does role-based code review work for cross-file implementation projects?▼

Role-based code review coordinates sequential handoffs to ensure architectural integrity for cross-file implementation projects. It enforces formal plan approval before execution, verifying that complex strategies are vetted by Analyst, Planner, and Plan-Reviewer roles.

When do I need a formal plan approval workflow for software architecture changes?▼

A formal plan approval workflow is needed for high-risk, multi-step, or architecture-sensitive implementation projects. It enforces rigorous verification and sequential role dispatch to ensure requirements are clear and strategies are vetted before any production code is touched.

Can I use automated planning depth selection for high-risk development tasks?▼

Automated planning depth selection evaluates the semantic risk of development tasks to choose between Light, Standard, or Thorough planning modes. This risk-gated approach ensures complex coding tasks receive the appropriate level of architectural review and verification.

What are the limitations of structured planning workflows for simple code changes?▼

Structured planning workflows are designed for complex, multi-step, or architecture-sensitive implementation projects. For simple code changes, enforcing sequential role dispatch and formal plan approval introduces unnecessary overhead and friction.