omc-plan

Plan complex initiatives through an interview-guided workflow with acceptance criteria and ADRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex initiatives often requires turning vague ideas into structured requirements and coordinating cross-functional input. This Skill provides a guided, consensus-ready approach that transitions from interviews to executable plans, reducing scope creep and misalignment.

Core Features & Use Cases

  • Auto-detects when to interview vs plan directly, ensuring efficient requirements gathering.
  • Supports consensus-driven planning via RALPLAN-DR, with Planner/Architect/Critic roles and review loops.
  • Manages a stateful lifecycle from planning to handoff, with explicit handoff behavior and safe termination.
  • Produces a plan with ADRs, acceptance criteria, and a clear path to execution saved under .omc/plans/.
  • Offers an interactive mode for user alignment and iterative improvements.

Quick Start

Tell me a planning goal and I will generate a structured plan using an interview-driven workflow, producing a consensus-ready plan and ADRs.

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 ideas into structured requirements for complex initiatives?

To turn vague ideas into structured requirements, you can use an interview-guided workflow that extracts details interactively, ensuring broad or detailed requests are captured efficiently before planning begins.

What's the best way to create a project plan with testable acceptance criteria and ADRs?

Creating a project plan with testable acceptance criteria and ADRs involves a structured workflow that generates a detailed plan, saves it under .omc/plans/, and provides a clear execution path from planning to handoff.

How does consensus-driven planning work for cross-functional team alignment?

Consensus-driven planning operates via RALPLAN-DR loops, utilizing Planner, Architect, and Critic roles with review cycles to coordinate cross-functional input and reduce scope creep or misalignment.

Can I skip the interview process for detailed planning requests?

Yes, you can skip the interview process using direct mode, which allows the system to auto-detect when to plan directly instead of interviewing, ensuring efficient requirements gathering for already detailed requests.

Does this structured planning workflow manage stateful lifecycles from planning to handoff?

Yes, this structured planning workflow manages a stateful lifecycle from planning to handoff, featuring explicit handoff behavior, safe termination, and optional interactive prompts for iterative user alignment.