omc-plan

Generate structured implementation work plans with consensus and review workflows.

Updated May 18, 2026
One-click install
npx skills add https://github.com/solitude6060/Yao-skills --skill omc-plan-solitude6060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-plan
Source: https://github.com/solitude6060/Yao-skills/tree/main/skills/plan
Command: npx skills add https://github.com/solitude6060/Yao-skills --skill omc-plan-solitude6060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of starting implementation without clear requirements, leading to rework and scope creep by producing a structured, quality-gated work plan (with optional multi-perspective consensus and review).

Core Features & Use Cases

  • Interview-first planning: Automatically detects broad/vague requests and runs an iterative interview to gather constraints before drafting a plan.
  • Consensus orchestration (RALPLAN-DR): Produces plans via a Planner → Architect → Critic loop, optionally interactive, with bounded iterations and a final ADR section.
  • Review mode: Evaluates an existing plan for quality using explicit criteria (testability, risk clarity, verification steps) and returns approve/revise/reject outcomes.
  • Handoff to execution: On approval, transitions to downstream execution via the appropriate orchestration surface (team or ralph) instead of executing directly inside the planning agent.

Quick Start

Run: plan a structured implementation roadmap for "add incident triage dashboards for our on-call workflow" using consensus mode with review gates.

Frequently Asked Questions about omc-plan

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

FAQPage Schema
How do I create a structured implementation plan for a vague software feature request?

Consensus planning orchestrates a Planner, Architect, and Critic loop to validate architecture and requirements, producing a quality-gated work plan with bounded iterations and an Architecture Decision Record section for complex features.

What is the best way to review an existing project plan for testability and risk clarity?

Reviewing an existing project plan involves evaluating it against explicit criteria like testable acceptance criteria, risk clarity, and verification steps, returning an approve, revise, or reject outcome to ensure readiness before execution.

How do I scope requirements and prevent scope creep before starting code implementation?

Scoping requirements before coding requires applying a structured planning workflow with testable acceptance criteria, risk identification, and optional interactive user gates to validate the project scope and prevent downstream rework.

When should I use consensus mode over direct planning for software architecture tasks?

Use consensus mode over direct planning for broad or complex software architecture tasks requiring multi-perspective validation, utilizing a Planner, Architect, and Critic loop to achieve quality-gated consensus before handing off to execution.