create-plan

davila7/claude-code-templates · Agent Skill

Generates a concise plan for coding tasks, outlining steps from research to deployment.

Overview

Publisher	davila7Community
Repository	davila7/claude-code-templates ↗
Skill folder	`create-plan`
Stars	30,563
Bundled files	1
License	MIT
Last updated	December 28, 2025
Links	Skill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security

low risk · no obvious risks found — the full report shows the details

Compatibility

needs extra software

Similar skills

144 similar skills found

Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “create-plan” skill from mozgi.io (https://mozgi.io/skills/create-plan/) for me.

1. Download the archive: https://mozgi.io/skills/create-plan/download
   If it fails, take the skill folder from the source: https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/create-plan
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “create-plan” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/create-plan/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

git clone --depth 1 --branch main https://github.com/davila7/claude-code-templates.git /tmp/claude-code-templates
mkdir -p .claude/skills
cp -r /tmp/claude-code-templates/cli-tool/components/skills/development/create-plan .claude/skills/create-plan

Restart Claude Code — the skill appears in the list; call it manually with /create-plan. For all projects use ~/.claude/skills.

git clone --depth 1 --branch main https://github.com/davila7/claude-code-templates.git /tmp/claude-code-templates
mkdir -p .agents/skills
cp -r /tmp/claude-code-templates/cli-tool/components/skills/development/create-plan .agents/skills/create-plan

Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $create-plan. For all projects use ~/.agents/skills.

git clone --depth 1 --branch main https://github.com/davila7/claude-code-templates.git /tmp/claude-code-templates
mkdir -p .cursor/skills
cp -r /tmp/claude-code-templates/cli-tool/components/skills/development/create-plan .cursor/skills/create-plan

Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.

git clone --depth 1 --branch main https://github.com/davila7/claude-code-templates.git /tmp/claude-code-templates
mkdir -p .gemini/skills
cp -r /tmp/claude-code-templates/cli-tool/components/skills/development/create-plan .gemini/skills/create-plan

Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.

Review the source files

1 file Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

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.md and 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)

Frequently asked questions

What does the create-plan skill do?

Generates a concise plan for coding tasks, outlining steps from research to deployment.

How do I install create-plan?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with create-plan?

Skills are plain Markdown instructions (the Agent Skills format), so create-plan works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is create-plan free?

The skill is published openly by davila7 under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →

agent-transcript Adds a redacted agent transcript to GitHub PR or issue bodies within OpenClaw agent-created workflows. openclaw389k

autoreview Automates code review using various AI models, providing structured reports and recommendations. openclaw389k

to-issues Breaks a plan or PRD into independently actionable issues. mattpocock304k

improve-codebase-architecture Scans a codebase for deepening opportunities and turns them into a prioritized visual report. mattpocock304k

triage Moves issues through a structured triage state machine. mattpocock304k

grill-with-docs Sharpens the domain model and updates supporting docs while grilling through design choices. mattpocock304k