create-plan

Solid

Design 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).

AI & Automation 10 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Plan Create a detailed implementation plan for changes to this workspace. Plans are thorough documents that capture the full context, rationale, and step-by-step tasks needed to execute a change with complete alignment across the project. ## Variables request: $ARGUMENTS (describe what you want to plan — new command, new workflow, structural change, template update, etc.) --- ## Instructions - **IMPORTANT:** You are creating a PLAN, not implementing changes. Research thoroughly, think deeply, then output a comprehensive plan document. - Use your reasoning capabilities to think hard about the request, workspace structure, and best approach. - Research the workspace to understand existing patterns, conventions, and how this change fits. - Create the plan in the `plans/` directory with filename: `YYYY-MM-DD-{descriptive-name}.md` - Use today's date - Replace `{descriptive-name}` with a short, kebab-case name (e.g., "add-guest-research-command", "restructure-outputs", "create-outreach-workflow") - Fill out every section of the Plan Format below. Replace all `<placeholders>` with specific, actionable content. - Be thorough — this plan will be executed by `/implement` and needs enough detail to execute without ambiguity. - Follow existing patterns. Study similar files in the workspace before proposing new structures. --- ## Research Phase Before writing the plan, investigate: 1. **Read core reference files:** - `CLAUDE.md` — workspace overview - `context/` — b...

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

AI & Automation Featured

create-plan

Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

2,489 Updated 5 days ago
foryourhealth111-pixel
AI & Automation Listed

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.

1 Updated 1 weeks ago
danielleit241
AI & Automation Solid

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.

0 Updated today
allemaar