Transform vague requests into auditable roadmaps with evidence and approval.
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill plan-yeachan-heo
Please help me install this Agent Skill. Skill: plan Source: https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/plan Command: npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill plan-yeachan-heo
This Skill turns vague project requests into concrete, auditable plans by orchestrating interactive requirements gathering, multi‑perspective validation, and formal plan outputs that guide execution.
Describe your goal and ask the plan to generate a work plan. Choose a mode (interview, direct, consensus, or review) based on your needs. The plan will guide you through one-question-at-a-time interviews when appropriate and save outputs to the designated folders.
High-intent search queries and answers about installing and using this skill.
Turning vague project ideas into actionable roadmaps involves interactive requirements gathering and multi-perspective validation. You can use interview mode for broad requests or direct planning mode for explicit specs, ensuring plans meet acceptance criteria and cite evidence before saving to .omc/plans.
The best way to validate project requirements before creating a work plan is using a consensus loop that cycles through Planner, Architect, and Critic roles. This multi-perspective validation ensures architectural soundness and applies quality gates before finalizing the roadmap.
Yes, you can review existing project plans against acceptance criteria and risk using the dedicated review workflow. This evaluates the plan's soundness and ensures it cites evidence from files and lines before granting user approval for execution.
Yes, the planning workflow requires explicit user approval before execution. Plans must cite evidence from specific files and lines, meet explicit acceptance criteria, and pass multi-perspective consensus validation to ensure auditable decision making.
To gather requirements when a project request is too broad, use the interactive interview mode. This mode guides you through one-question-at-a-time discovery sessions to transform vague requests into concrete, auditable roadmaps stored in .omc/drafts.
evolution-foundationGenerate strategic engineering plans from user requests with quality gates.
INNERJOINTTrace root causes and produce interview-driven specifications for downstream planning.
cheafiConvert ambiguous task requests into explicit consensus plans via Planner/Architect/Critic refinement.
wmasfoeAutomate strategic planning with interview-driven discovery or direct plan generation.
