create-plan
SolidDesign a structured implementation plan for a non-trivial change before any code is written - objective, scope, critical files, step sequence, success criteria, and risks. Use before significant additions or multi-file work. Trigger when the user says "create plan", "plan for [change]", or "design the approach". Do NOT use to execute an existing plan (use /implement).
Install
Quality Score: 80/100
Skill Content
Details
- Author
- mishahanin
- Repository
- mishahanin/heading-os
- Created
- 3 weeks ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
create-plan
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
plan
Use when the user asks for an implementation plan, technical strategy, or phased approach before coding a non-trivial change. Produce one durable `plan.md` containing the design contract, ordered work, verification, risks, and status. Gather scout or research evidence only when uncertainty affects the plan; do not create separate phase files by default.
plan-create
Propose a phased, gated implementation plan before any work begins. Trigger when the user runs /plan-create, says "make a plan", "plan this out", "design before coding", "let's plan first", "architect this", or asks for a phased approach before implementation. Also trigger proactively when a task is complex enough that jumping straight to execution would be risky — multi-file changes, new features, architectural shifts, refactors spanning multiple components, or any task where misalignment early would be expensive to fix later. Output: a structured PLAN.md with phases, changes, risks, and verification criteria. Design only — no implementation code is written during /plan-create. Use plan-phases to restructure an existing plan, plan-execute to run an approved plan, plan-deep-dive to inspect a plan, plan-evolve to evolve shipped work, and plan-cleanup after execution.