plan

Converts a feature idea into an atomic, approved implementation plan through deep research and a 4-pass specification.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill plan-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/manusco/wolfgang/tree/main/.cursor/skills/plan
Command: npx skills add https://github.com/manusco/wolfgang --skill plan-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague feature idea into an actionable implementation plan often skips research and produces vague specs. This Skill routes the /plan command to a structured planning procedure that performs deep research and a 4-pass specification process, producing an atomic, approved implementation plan. ## Core Features & Use Cases - Command Routing: Maps the /plan command to the full planning procedure defined in .agents/skills/strategy/plan/SKILL.md. - Deep Research Planning: Executes a research-driven, 4-pass specification workflow before any code is written. - Definition of Done Enforcement: Follows an explicit Definition of Done so plans meet approval criteria. - Use Case: You have a rough idea for a new API endpoint. Invoke /plan to research the codebase, iterate through specification passes, and produce an atomic implementation plan ready for approval and execution. ## Quick Start Ask the assistant to run /plan for your feature idea, for example: plan the implementation of a user notification preferences page.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a feature idea into an implementation plan?▼

Invoke the /plan command with your feature idea. The Skill routes to a planning procedure that performs deep research and a 4-pass specification, producing an atomic plan that must satisfy a Definition of Done before approval.

What is a 4-pass specification in implementation planning?▼

A 4-pass specification iterates over the plan four times to refine research, scope, and implementation details. The exact passes are defined in the referenced strategy plan procedure file, which this Skill executes in full.

Does the plan Skill write code or only produce plans?▼

It only produces implementation plans. The Skill routes /plan to a planning procedure focused on research and specification; actual coding happens after the plan is approved through its Definition of Done.

Where is the actual planning procedure defined?▼

The procedure lives in .agents/skills/strategy/plan/SKILL.md. This Skill is only a router: it reads that file in full and executes it exactly, so the referenced file must exist for the command to work.

When should I not use a structured planning workflow?▼

Skip it for trivial changes like typo fixes or one-line edits where research and multi-pass specification add overhead without value. The workflow is designed for features or ideas that need atomic, approved plans.