plan

Create execution work plans with requirements, acceptance criteria, and verification steps.

Updated May 5, 2026
One-click install
npx skills add https://github.com/HyperionBurn/searchv1beta --skill plan-hyperionburn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/HyperionBurn/searchv1beta/tree/main/.github/skills/plan
Command: npx skills add https://github.com/HyperionBurn/searchv1beta --skill plan-hyperionburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert ambiguous or broad goals into a structured, executable work plan with clear next steps and acceptance criteria, reducing misalignment and rework.

Core Features & Use Cases

  • Interview-first planning for vague requests: Uses an interactive Q&A flow to gather scope, preferences, and constraints before drafting.
  • Direct planning for detailed requests: Skips the interview and generates a comprehensive plan immediately when requirements are already specific.
  • Consensus planning loop: Runs a Planner → Architect → Critic sequence, presenting trade-offs and allowing rejection-driven iteration.
  • Plan review and approval gates: Supports approval decisions and saves plans to .omg/plans/ for later review.
  • Use Case: You need to plan an outreach automation project in the UAE/GCC context—start with a broad goal like “map recruiter contacts and verify outreach targets,” then refine requirements and produce a step-by-step plan with risks, mitigations, and verification steps.

Quick Start

Use this plan skill to create an execution-ready plan by saying: “plan this recruiter outreach workflow for the UAE/GCC, include verification and scoring, and list acceptance criteria and risks.”

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 requirements into an actionable work plan?

To turn vague project requirements into an actionable work plan, use an interview-first planning approach that gathers scope, preferences, and constraints through interactive questions before drafting structured execution steps.

What is the best way to structure strategic planning for an ambiguous project goal?

The best way to structure strategic planning for an ambiguous project goal is running a consensus loop that applies a Planner, Architect, and Critic sequence to present trade-offs, allow rejection-driven iteration, and finalize approval gates.

How do I generate an execution plan with acceptance criteria and risk mitigations?

To generate an execution plan with acceptance criteria and risk mitigations, provide your specific project details to trigger a direct planning workflow that outputs structured implementation steps, file references, and verification steps immediately.

Can I use an interactive requirements gathering workflow for broad project requests?

Yes, you can use an interactive requirements gathering workflow for broad project requests by engaging an interview mode that uses question hooks to extract specific scope and constraints before saving the finalized plan for execution.

Does this planning workflow support approval gates and saving plans for later execution?

Yes, this planning workflow supports approval gates by applying review decisions and saving the finalized structured outputs, including requirements summaries and implementation steps, directly to a designated directory for later execution.