One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill plan-realsigridjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/plan
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill plan-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents rework, scope creep, and missed edge cases by transforming vague or complex requests into structured, actionable plans before implementation begins.

Core Features & Use Cases

  • Adaptive Planning: Automatically chooses interview or direct planning based on request specificity.
  • Consensus and Review Workflows: Uses Planner, Architect, and Critic perspectives to validate high-stakes plans or evaluate existing plans.
  • Quality-Gated Outputs: Produces plans with requirements summaries, testable acceptance criteria, file-specific implementation steps, risks, mitigations, and verification steps.
  • Use Case: For a cross-cutting authentication feature, this Skill gathers codebase facts, clarifies requirements one question at a time, identifies risks, and saves an implementation-ready plan for execution by a dedicated engineering workflow.

Quick Start

Use the plan skill to create a detailed, testable implementation plan for the requested feature and save it to the project planning directory.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn vague software requests into actionable implementation plans?

To turn vague software requests into actionable implementation plans, use an adaptive workflow that conducts requirements interviews, extracts codebase facts, and generates testable acceptance criteria with file-specific implementation steps and risk mitigations.

What is consensus validation in software architecture planning?

Consensus validation in software architecture planning is a review workflow that evaluates high-stakes plans using Planner, Architect, and Critic perspectives to ensure quality-gated outputs before execution proceeds.

How do I write testable acceptance criteria for complex features?

Writing testable acceptance criteria for complex features requires gathering codebase facts and clarifying requirements one question at a time to produce explicit, verifiable conditions that must be met before implementation proceeds.

Can I use requirements gathering workflows for existing software plans?

Yes, requirements gathering workflows can evaluate existing plans through a review process that applies Planner, Architect, and Critic perspectives to validate risks, mitigations, and verification steps before consensus plans proceed to execution.

What are the limitations of automated codebase analysis for requirements gathering?

Automated codebase analysis for requirements gathering requires explicit approval before consensus plans proceed to execution, meaning it cannot bypass human validation for high-stakes architectural decisions or automatically resolve scope creep without interview-based clarification.