plan

Generate structured work plans with ADRs, acceptance criteria, and risk mitigations.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill plan-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/plan
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill plan-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan provides a structured, repeatable method to turn vague goals into concrete, executable plans, reducing ambiguity and rework by clarifying scope and milestones, and by selecting the appropriate planning flow (interview or direct) and governance (consensus or review) to fit the task.

Core Features & Use Cases

  • Auto-detect interview vs direct mode based on request specificity to choose the appropriate planning flow.
  • Supports Consensus mode with Planner/Architect/Critic loop (RALPLAN-DR) and a Review mode for evaluating existing plans.
  • Modes include Interview, Direct, Consensus, Consensus Interactive, and Review; interactive feedback steps ensure user alignment.
  • Outputs include ADRs, testable acceptance criteria, and structured implementation steps; artifacts are saved to .omx/plans/ and .omx/drafts/ with clear traceability.
  • Integrates with downstream execution by enabling handoff to ralph or team for implementation.

Quick Start

Describe your goal and I will generate a structured plan using interview, direct, or consensus modes.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn vague project goals into actionable work plans with risk mitigations?

Work plans are created through intelligent interaction that clarifies scope and milestones, selecting a direct or interview planning flow. This process outputs structured implementation steps, ADRs, acceptance criteria, and risk mitigations to reduce ambiguity and rework.

What is the consensus workflow for requirements planning and quality enforcement?

Consensus workflows use a Planner, Architect, and Critic loop to evaluate requirements planning. This governance mechanism enforces quality standards, requires file and line citations, and ensures user alignment through interactive feedback steps before finalizing the output.

How do I evaluate an existing project plan to ensure it meets quality standards?

You can evaluate an existing project plan using the Review mode. This mode assesses current plans against quality standards, checking for structured implementation steps, ADRs, acceptance criteria, and risk mitigations to ensure completeness and traceability.

Does the planning flow auto-detect when to interview me versus plan directly?

Yes, the planning flow auto-detects whether to interview or plan directly based on request specificity. It chooses the appropriate planning flow automatically, ensuring the level of interaction matches the clarity of your initial goal.

How are architecture decision records and acceptance criteria structured in the output?

Architecture decision records and testable acceptance criteria are structured within the comprehensive output. Artifacts are saved to designated plans and drafts directories with clear traceability, integrating file and line citations to support downstream execution.

Can I hand off the generated plan to team members for implementation?

Yes, you can hand off the generated plan to team members for implementation. The output artifacts integrate with downstream execution by enabling direct handoff, ensuring the structured steps and acceptance criteria are actionable.