plan-create

Generates a phased, gated implementation plan as a structured PLAN.md artifact.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill plan-create-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-create
Source: https://github.com/allemaar/open-skills/tree/main/skills/plan-create
Command: npx skills add https://github.com/allemaar/open-skills --skill plan-create-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into code on complex, multi-file tasks often leads to misalignment, scope creep, and expensive rework. This Skill enforces a design-first workflow that produces a reviewed, testable implementation plan before any code is written. ## Core Features & Use Cases - Phased planning protocol: Runs five gated phases (pre-flight, problem & scope, implementation design, risk & verification, plan production) with explicit abort and recovery rules at each gate. - Structured PLAN.md output: Produces a standardized plan artifact with success criteria, scope boundaries, phased changes, dependency mapping, a risk register, and an executable verification plan. - Full and Fast modes: Defaults to a thorough Full mode, with an opt-in Fast mode for single-unit changes that condenses phases while never skipping gates or the user alignment checkpoint. - Use Case: Before refactoring authentication across multiple services, run the planning protocol to get a PLAN.md with testable success criteria, a HIGH-risk mitigation table, and per-phase verification commands your team can approve and execute. ## Quick Start Ask the agent to run /plan-create and make a phased plan for your task before writing any code.

Frequently Asked Questions about plan-create

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

FAQPage Schema
How do I create an implementation plan before coding with an AI agent?

Invoke /plan-create or ask the agent to make a plan. The skill runs a five-phase gated protocol covering pre-flight context loading, problem definition, design, risk analysis, and plan production, then writes a structured PLAN.md without writing any implementation code.

What should a good software implementation plan include?

A solid plan includes testable success criteria, explicit in-scope and out-of-scope boundaries, phased changes with estimates, a dependency map, a risk register with mitigations, and a verification plan with executable pass/fail tests for each criterion.

When should I use Fast mode instead of Full mode?

Use Fast mode only for a single unit of work with no cross-component impact and no external dependencies, and you must state that reason explicitly. Gates and the user alignment checkpoint are never skipped; only pre-flight load steps and phase separation are condensed.

Does plan-create write any implementation code?

No. The skill is design-only by hard rule. Its sole deliverable is the PLAN.md artifact; execution is handled separately by the plan-execute skill after the plan is reviewed and approved.

What happens when a planning gate fails?

Warning-level findings are logged in the Gate Summary and planning proceeds. An ABORT-level finding, such as untestable success criteria or an unmitigated HIGH risk, stops the protocol, surfaces the issue to the user, and waits for confirmation before continuing.