omc-plan

Produce strategic, testable work plans from user goals for Claude Code workflows.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill omc-plan-dropsyoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-plan
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/plan
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill omc-plan-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you stop guessing requirements by producing a comprehensive, actionable work plan before you start building.

Core Features & Use Cases

  • Interview or direct planning: automatically chooses a requirements-gathering interview for broad/vague requests, or plans immediately for detailed requests.
  • Consensus planning for correctness: supports iterative Planner → Architect → Critic loops (including RALPLAN-DR structured deliberation) to reduce blind spots.
  • Review and improvement loop: can review an existing plan and iteratively revise until quality gates (testable acceptance criteria and mitigations) are met.
  • Safe, gated handoff to execution: prompts for approval in interactive flows and then hands off to execution skills rather than coding during planning.

Quick Start

Run omc-plan with a clear goal: plan this feature for our app, including scope, acceptance criteria, and verification steps.

Frequently Asked Questions about omc-plan

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

FAQPage Schema
How do I turn vague project requirements into testable work plans?

To turn vague requirements into testable work plans, you need structured requirements gathering and consensus planning. This involves iterative Planner, Architect, and Critic loops to define scope, acceptance criteria, and verification steps before execution begins.

What is consensus planning and how does it reduce blind spots in software architecture?

Consensus planning reduces blind spots in software architecture by applying iterative Planner, Architect, and Critic loops, including structured RALPLAN-DR deliberation. This multi-perspective review process ensures architectural decisions meet quality gates before execution.

How do I review and improve an existing project plan to meet quality gates?

Reviewing an existing project plan involves iteratively revising it until quality gates are met. This process validates that testable acceptance criteria and risk mitigations are present, ensuring the plan is safe for execution handoff.

Can I generate Architecture Decision Records directly from requirements gathering workflows?

Yes, generating Architecture Decision Records (ADR) is supported directly within requirements gathering workflows. The planning process outputs ADRs alongside testable work plans to document architectural decisions made during the consensus planning phase.

Does automated planning work better with direct input or interview-based requirements scoping?

Automated planning supports both direct input and interview-based requirements scoping. It automatically chooses immediate planning for detailed requests, while initiating a requirements-gathering interview for broad or vague project goals.