plan

Generates structured work plans through interview, direct, consensus, and review modes.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill plan-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/plan
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill plan-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping into code without understanding requirements leads to rework, scope creep, and missed edge cases. This Skill turns broad or vague requests into comprehensive, quality-gated work plans with testable acceptance criteria before any implementation begins. ## Core Features & Use Cases - Adaptive Interview Mode: Auto-detects vague requests and gathers requirements one focused question at a time, using codebase exploration to ask informed questions instead of guessing. - Consensus Mode (RALPLAN-DR): Runs a sequential Planner, Architect, and Critic deliberation loop with principles, decision drivers, viable options, and a final ADR section for high-stakes plans. - Review Mode: Evaluates existing plans against quality criteria such as 80% file/line citations and 90% testable criteria, returning APPROVED, REVISE, or REJECT verdicts. - Use Case: A user says "plan the migration of our auth system". The Skill interviews for scope and constraints, explores the codebase for existing auth patterns, then produces a plan saved to .omx/plans/ with risks, mitigations, and verification steps. ## Quick Start Ask the assistant to plan your next feature or refactor, for example by saying "plan the migration of our authentication system to JWT".

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a work plan before writing code?

Describe your task and the Skill auto-detects the right mode: broad requests trigger an interactive interview that gathers requirements one question at a time, while detailed requests generate a plan directly. Plans are saved to .omx/plans/ with acceptance criteria and verification steps.

What is consensus mode in plan generation?

Consensus mode runs a sequential Planner, Architect, and Critic loop using RALPLAN-DR structured deliberation. It produces principles, decision drivers, viable options, and a final ADR section, iterating up to five times until the Critic approves the plan.

How do I review an existing implementation plan?

Use review mode with the --review flag or by asking to review a plan. A Critic evaluates the plan against quality criteria such as 80% file/line citations and 90% testable criteria, returning APPROVED, REVISE with feedback, or REJECT.

When should I not use a planning workflow?

Skip planning for simple questions answerable directly, single focused fixes with obvious scope, or when you want autonomous end-to-end execution. In those cases answer directly, implement the fix, or use an execution-oriented workflow instead.

Does the planning skill execute the code changes itself?

No. The planning agent never implements directly. After approval it hands off to execution workflows such as ultragoal for durable goal execution or team for coordinated parallel implementation, passing the approved plan path as context.