Create Plan
- 503 installs
- 30.1k repo stars
- Updated August 4, 2026
- davila7/claude-code-templates
create-plan is a Claude Code skill that turns a vague product idea or feature request into a clear, ordered implementation plan for developers who want a coding agent to execute a scoped build without writing files durin
About
create-plan from davila7/claude-code-templates turns a user prompt into a single actionable implementation plan delivered in the final assistant message. The skill operates entirely in read-only mode without writing or updating files during planning. It scans README.md, docs/, CONTRIBUTING.md, and ARCHITECTURE.md, skims files most likely to be touched, and identifies constraints including language, frameworks, CI test commands, and deployment shape before asking follow-up questions only when necessary. Developers reach for create-plan when they explicitly ask for a plan related to a coding task and want a concise, ordered execution roadmap their agent can follow.
- Converts high-level specs into ordered task lists with acceptance criteria
- Produces ready-to-execute plans for Claude Code, Cursor, and similar agents
- Includes explicit next-skill handoff to implementation workflows
- Reduces scope creep and context loss between planning and coding
Create Plan by the numbers
- 503 all-time installs (skills.sh)
- Ranked #761 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill create-planAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 503 |
|---|---|
| repo stars | ★ 30.1k |
| Last updated | August 4, 2026 |
| Repository | davila7/claude-code-templates ↗ |
How do you plan a coding task for an agent?
Turn a vague product idea or feature request into a clear, ordered implementation plan their coding agent can execute.
Who is it for?
Developers who want a read-only, codebase-informed implementation plan before handing execution to a coding agent.
Skip if: Teams that need immediate code changes, grant research, or multi-week product roadmap documents with stakeholder formatting.
When should I use this skill?
The user explicitly asks for a plan related to a coding task or feature implementation.
What you get
Single ordered implementation plan with identified constraints, touched files, and follow-up questions in the final assistant message.
- Ordered implementation plan
- Identified codebase constraints
Files
Create Plan
Goal
Turn a user prompt into a single, actionable plan delivered in the final assistant message.
Minimal workflow
Throughout the entire workflow, operate in read-only mode. Do not write or update files.
1. Scan context quickly
- Read
README.mdand any obvious docs (docs/,CONTRIBUTING.md,ARCHITECTURE.md). - Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
2. Ask follow-ups only if blocking
- Ask at most 1–2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
3. Create a plan using the template below
- Start with 1 short paragraph describing the intent and approach.
- Clearly call out what is in scope and what is not in scope in short.
- Then provide a small checklist of action items (default 6–10 items).
- Each checklist item should be a concrete action and, when helpful, mention files/commands.
- Make items atomic and ordered: discovery → changes → tests → rollout.
- Verb-first: "Add…", "Refactor…", "Verify…", "Ship…".
- Include at least one item for tests/validation and one for edge cases/risk when applicable.
- If there are unknowns, include a tiny Open questions section (max 3).
4. Do not preface the plan with meta explanations; output only the plan as per template
Plan template (follow exactly)
# Plan
<1–3 sentences: what we're doing, why, and the high-level approach.>
## Scope
- In:
- Out:
## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>
## Open questions
- <Question 1>
- <Question 2>
- <Question 3>Checklist item guidance
Good checklist items:
- Point to likely files/modules: src/..., app/..., services/...
- Name concrete validation: "Run npm test", "Add unit tests for X"
- Include safe rollout when relevant: feature flag, migration plan, rollback note
Avoid:
- Vague steps ("handle backend", "do auth")
- Too many micro-steps
- Writing code snippets (keep the plan implementation-agnostic)
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Choose create-plan for concise read-only implementation planning rather than long-running multi-agent orchestration or documentation auditing.
FAQ
Does create-plan modify any project files?
create-plan operates in read-only mode throughout the entire workflow. The skill scans README, docs, and relevant source files but does not write or update files, delivering only a single actionable plan in the final message.
What context does create-plan scan before planning?
create-plan reads README.md, docs/, CONTRIBUTING.md, and ARCHITECTURE.md, then skims files most likely to be touched. The skill identifies language, frameworks, CI test commands, and deployment constraints before producing the plan.