omc-plan

Plan projects through interviews, consensus reviews, and structured artifacts.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Pryma-Tech/iris --skill omc-plan-pryma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-plan
Source: https://github.com/Pryma-Tech/iris/tree/main/cli/skills/plan
Command: npx skills add https://github.com/Pryma-Tech/iris --skill omc-plan-pryma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan creates comprehensive, actionable work plans through intelligent interaction. It auto-detects whether to interview the user (broad requests) or plan directly (detailed requests), and supports consensus mode (iterative Planner/Architect/Critic loop with RALPLAN-DR structured deliberation) and review mode (Critic evaluation of existing plans).

Core Features & Use Cases

  • Auto-detect interview vs direct mode based on request specificity
  • Consensus planning with Planner -> Architect -> Critic loop and RALPLAN-DR deliberation
  • Interactive prompts and guided user alignment during consensus mode
  • State management for ralplan stop hooks, handoffs to execution, and post-review workflows
  • Review path for Critic evaluation and plan refinement

Quick Start

Describe your planning goal and constraints, and I will generate a structured plan.

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 project plan for high-stakes, multi-disciplinary work?

Structured planning for high-stakes projects is created by running coordinate interviews, direct planning, and consensus reviews to produce a testable plan. The workflow enforces a strict state lifecycle and requires ADRs and plan artifacts stored under .omc/plans/.

What is consensus planning and how does an interactive Planner, Architect, and Critic loop work?

Consensus planning uses an iterative Planner, Architect, and Critic loop with RALPLAN-DR structured deliberation. This interactive mode guides user alignment through prompts, generating multi-disciplinary input and formal approvals before finalizing the plan.

When do I need formal ADRs and plan artifacts for workflow execution?

You need formal ADRs and plan artifacts when managing vague, high-stakes projects that require formal approvals. The strict state lifecycle enforces these artifacts to ensure structured execution and testable outcomes stored under .omc/plans/.

Can I evaluate and refine an existing plan through a formal review process?

Yes, you can evaluate existing plans using the review path. The Critic evaluates the structured plan and refines it through iterative feedback, ensuring the workflow meets formal approval standards before execution handoff.

Does the planning workflow auto-detect whether to interview users or plan directly?

Yes, the workflow auto-detects the planning mode based on request specificity. Broad requests trigger interactive interviews to gather constraints, while detailed requests proceed to direct planning for immediate structured output.

What are the limitations of using a strict state lifecycle for consensus planning?

The strict state lifecycle requires formal ADRs and plan artifacts, adding overhead to simple tasks. Consensus planning is designed for vague, high-stakes projects, so low-complexity workflows may find the interactive Planner, Architect, and Critic deliberation excessive.