ralplan

Guide teams through planning, review, and decision-making before executing significant tasks.

2|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/r3dlex/oh-my-auggie --skill ralplan-r3dlex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/r3dlex/oh-my-auggie/tree/main/plugins/oma/skills/ralplan
Command: npx skills add https://github.com/r3dlex/oh-my-auggie --skill ralplan-r3dlex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams and individuals achieve explicit agreement before proceeding with significant or potentially disruptive actions, reducing miscommunication and errors.

Core Features & Use Cases

  • Pre-Execution Approval: Facilitates structured planning and review processes for complex tasks.
  • Decision Documentation: Guides users through drafting options, evaluating trade-offs, and recording consensus.
  • Use Case: For a team implementing a major architecture change, use this Skill to collaboratively evaluate options, address concerns, and only proceed once agreement is reached.

Quick Start

Use the ralplan skill to define a consensus process for deploying a new feature, including problem description, options, and decision criteria.

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I ensure team consensus before executing critical software changes?

To ensure team consensus before executing critical software changes, you can use a structured planning process to collaboratively evaluate options, address concerns, and record explicit agreement before proceeding. This reduces miscommunication and deployment risks.

What is the best way to document team decision-making for a major architecture change?

Documenting team decision-making for a major architecture change involves drafting available options, evaluating trade-offs against decision criteria, and recording the final team consensus. This structured review process prevents misalignment and errors.

Can I use a structured review process to get pre-execution approval for deploying a new feature?

Yes, you can use a structured review process to get pre-execution approval for deploying a new feature. By defining the problem, outlining options, and establishing decision criteria, teams can collaboratively review and approve significant tasks.

When do I need a formal consensus process for software engineering tasks?

You need a formal consensus process for software engineering tasks when facing significant or potentially disruptive actions, such as major architecture changes or complex deployments. It ensures team alignment and reduces the risk of errors before execution.

Does this team planning approach work for individual developers evaluating complex task options?

Yes, this team planning approach works for individual developers by guiding them through a structured evaluation of options, trade-offs, and decision criteria. It helps individuals achieve explicit agreement and thorough planning before executing significant tasks.