make-plan
Generates a structured plan for development work without modifying files.
Install
mkdir -p .claude/skills/make-plan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13082" && unzip -o skill.zip -d .claude/skills/make-plan && rm skill.zipInstalls to .claude/skills/make-plan
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create an implementation or investigation plan from the user's proposal, requirement, or idea. Use when the user invokes `make_plan` or `make-plan`, or asks for a plan before coding. The expected output is a plan only; do not modify files unless the user later asks to implement.Key capabilities
- →Extract objective, constraints, target files, and success criteria
- →Inspect the repository for plan concreteness
- →State assumptions when safe
- →Ask concise clarification questions
- →Name likely files or modules for code changes
How it works
The skill extracts objective, constraints, target files, and success criteria from the user's input and relevant chat context, then inspects the repository to make the plan concrete.
Inputs & outputs
When to use make-plan
- →Plan new feature implementation
- →Draft investigation roadmap
- →Create task plan
About this skill
Make Plan
Workflow
- Extract the objective, constraints, target files, and success criteria from the user's latest proposal and relevant chat context.
- Inspect the repository only as much as needed to make the plan concrete. Prefer
rg,rg --files, and short file reads. - State assumptions instead of asking questions when a reasonable assumption is safe. Ask one concise clarification question only when the plan would be misleading without the answer.
- Do not edit files, stage changes, create commits, or run destructive commands while using this skill.
- If the plan involves code changes, name likely files or modules to inspect or modify and include validation commands.
Plan Output
Structure the plan so the user can approve, reject, or modify it quickly:
- Goal: one sentence describing the intended outcome.
- Assumptions: concrete assumptions that affect the plan.
- Scope: what is included and what is intentionally excluded.
- Steps: ordered implementation or investigation steps.
- Validation: tests, scripts, review checks, or manual verification.
- Risks: edge cases, migration concerns, rollback issues, or unresolved decisions.
Keep the plan concise, but make each step actionable enough that another Codex session could execute it.
When not to use it
- →When the user wants immediate file modifications
- →When the user does not need a plan before coding
Limitations
- →Does not modify files
- →Does not stage changes
- →Does not create commits
How it compares
This skill structures a plan with specific sections like Goal, Assumptions, Scope, Steps, Validation, and Risks, unlike an unstructured approach which may miss key planning elements.
Compared to similar skills
make-plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| make-plan (this skill) | 0 | 3mo | No flags | Beginner |
| create-plan | 36 | 8mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
| system-design | 19 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.