omc-plan

Generate strategic work plans from user goals via interview, consensus, or review workflows.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/marcmunoz-uno/jailbreak --skill omc-plan-marcmunoz-uno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-plan
Source: https://github.com/marcmunoz-uno/jailbreak/tree/main/skills/plan
Command: npx skills add https://github.com/marcmunoz-uno/jailbreak --skill omc-plan-marcmunoz-uno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted effort by translating broad or ambiguous requests into comprehensive, testable plans before any implementation begins.

Core Features & Use Cases

  • Interview-driven planning for vague requests: Detects when requirements are unclear, then gathers focused inputs one at a time (optionally with user prompts) to scope the work correctly.
  • Quality-gated consensus planning (Planner/Architect/Critic): Runs a structured loop that validates assumptions, explores alternatives, and strengthens acceptance criteria and risk mitigations.
  • Review and iteration support: Critically evaluates existing plans, or revises plans up to bounded iteration limits based on reviewer feedback.
  • Plan outputs with verifiability artifacts: Produces a plan file designed for downstream execution, including acceptance criteria and, in consensus mode, RALPLAN-DR plus ADR (and pre-mortem/test plan in deliberate mode).

Quick Start

Tell the agent to plan your work by saying: "Plan this: <your goal or project description>."

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 goals into actionable execution plans?

To turn vague project goals into actionable execution plans, use an interview-driven planning workflow that gathers focused requirements one at a time. This approach scopes broad requests correctly by detecting unclear inputs and collecting targeted information before generating a structured work plan.

What is consensus workflow planning and how does it improve requirements gathering?

Consensus workflow planning improves requirements gathering by running a sequential Planner, Architect, and Critic quality gate loop. This structured process validates assumptions, explores alternatives, and strengthens acceptance criteria and risk mitigations before producing execution-ready deliverables.

Can I use architecture review and ADRs to evaluate existing strategic plans?

Yes, you can evaluate existing strategic plans through a dedicated review workflow that critically assesses current plans and produces Architecture Decision Records (ADRs). It supports iterative revision loops bounded by iteration limits based on reviewer feedback to validate or revise your existing architecture.

How do I generate testable acceptance criteria and risk mitigation strategies for a new project?

Generate testable acceptance criteria and risk mitigation strategies by applying a quality-gated consensus planning loop. This mechanism enforces structured requirements gathering and sequential validation to ensure all deliverables include verifiable artifacts like pre-mortem and test plans.

What is the best way to scope broad requests before downstream implementation begins?

The best way to scope broad requests before implementation is to apply state-safe handoff logic within a direct or consensus workflow. This prevents wasted effort by translating ambiguous requests into comprehensive, testable plans with clear acceptance criteria for downstream execution modes.