plan

Generate structured work plans with PRD and test-spec artifacts.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill plan-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/plan
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill plan-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan turns broad, unclear requests into structured, actionable work plans so you can move from ambiguity to an approved implementation direction.

Core Features & Use Cases

  • Interview, direct, and review modes that match how specific your request is, while supporting reviewer-only evaluation of an existing plan.
  • Consensus planning that runs a Planner → Architect → Critic loop using structured RALPLAN-DR deliberation via direct flags such as --consensus.
  • Mode-safe handoff that prevents direct implementation and instead produces planning artifacts suitable for execution by downstream skills.

Quick Start

Use the plan skill to create a work plan for your change: submit the request as /omagy:plan "clarify and plan the change".

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a vague software request into an actionable work plan?

To turn a vague software request into an actionable work plan, you can use automated planning workflows that gather requirements, drive multi-perspective consensus, and produce structured PRD and test-spec artifacts for handoff.

What is consensus planning and when should I use it for requirements gathering?

Consensus planning is a structured deliberation loop involving Planner, Architect, and Critic roles. Use consensus planning for requirements gathering when a broad task requires multi-perspective decision making and evidence-backed acceptance criteria before implementation.

How do I generate PRDs and test specs before starting implementation?

You generate PRDs and test specs by enforcing planning-only responsibilities through lifecycle gating. This prevents direct implementation and instead produces structured planning artifacts suitable for execution by downstream skills.

Can I use an interview mode for scoping unclear software engineering tasks?

Yes, you can use interview mode for scoping unclear software engineering tasks. Interview mode matches how specific your request is and helps gather detailed requirements when the initial project boundaries are ambiguous.

What is the best way to evaluate an existing implementation plan?

The best way to evaluate an existing implementation plan is using a review workflow. This supports reviewer-only evaluation of an existing plan, ensuring the proposed strategy meets strict lifecycle gating and evidence-backed acceptance criteria.

Why does the planning workflow prevent direct code implementation?

The planning workflow prevents direct code implementation to satisfy strict lifecycle gating and enforce planning-only responsibilities. This ensures the output remains a strategic, actionable work plan rather than executable code, providing mode-safe handoff to downstream skills.