A command for creating detailed implementation plans through research and discussion. It can use task files, ticket references, and related links as input.

Use it to investigate a change, document the proposed approach, and refine the plan with the user.

It helps turn an incomplete request into an agreed sequence of technical work before implementation begins.

How buildonspark/spark configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to buildonspark/spark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/buildonspark/spark/main/.claude/commands/create_plan.md

Clone the repo

git clone --depth 1 https://github.com/buildonspark/spark

Made for: Claude Code.

Or install spark, the plugin that ships this one along with the rest of its 3 skills, 15 commands, 6 agents, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/buildonspark/spark/create_plan/github.svg)](https://agentmods.dev/commands/buildonspark/spark/create_plan)

Your own site

<a href="https://agentmods.dev/commands/buildonspark/spark/create_plan"><img src="https://agentmods.dev/badge/commands/buildonspark/spark/create_plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/buildonspark/spark/create_plan"><img src="https://agentmods.dev/badge/commands/buildonspark/spark/create_plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,134 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.03134
Opus 5.5	$0.00004	$0.01254
Sonnet 5.5	$0.00002	$0.00627
Haiku 4.5	$0.00001	$0.00313

Measured 1mo ago against content hash b1d10d357f72, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create_plan scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- [ ] API endpoint returns 200: `curl localhost:8080/api/new-endpoint`

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

create_plan_generic — 98% identical, 7 lines differ
create_plan — 94% identical, 19 lines differ
create_plan_nt — 89% identical, 37 lines differ
create_plan_nt — 89% identical, 39 lines differ

.claude/commands/create_plan.md · 443 lines

How it starts

The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementation Plan

You are tasked with creating detailed implementation plans through an interactive, iterative process. You should be skeptical, thorough, and work collaboratively with the user to produce high-quality technical specifications.

Initial Response

When this command is invoked:

Check if parameters were provided:
- If a file path or ticket reference was provided as a parameter, skip the default message
- Immediately read any provided files FULLY
- Begin the research process
If no parameters provided, respond with:

I'll help you create a detailed implementation plan. Let me start by understanding what we're building.

Please provide:
1. The task/ticket description (or reference to a ticket file)
2. Any relevant context, constraints, or specific requirements
3. Links to related research or previous implementations

I'll analyze this information and work with you to create a comprehensive plan.

Tip: You can also invoke this command with a ticket file directly: `/create_plan thoughts/allison/tickets/eng_1234.md`
For deeper analysis, try: `/create_plan think deeply about thoughts/allison/tickets/eng_1234.md`

Then wait for the user's input.

Process Steps

Step 1: Context Gathering & Initial Analysis

Read all mentioned files immediately and FULLY:
- Ticket files (e.g., thoughts/allison/tickets/eng_1234.md)
- Research documents
- Related implementation plans
- Any JSON/data files mentioned
- IMPORTANT: Use the Read tool WITHOUT limit/offset parameters to read entire files
- CRITICAL: DO NOT spawn sub-tasks before reading these files yourself in the main context
- NEVER read files partially - if a file is mentioned, read it completely
Spawn initial research tasks to gather context: Before asking the user any questions, use specialized agents to research in parallel:
- Use the codebase-locator agent to find all files related to the ticket/task
- Use the codebase-analyzer agent to understand how the current implementation works
- If relevant, use the thoughts-locator agent to find any existing thoughts documents about this feature
- If a Linear ticket is mentioned, use the linear-ticket-reader agent to get full details

Read the full file on GitHub · 443 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 443 lines · 9 tokens per session scan A b1d10d357f72

Subscribe to this mod's changes

create_plan is a command published in the GitHub repository buildonspark/spark (113 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,134 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Planning

spark: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

Copies of this mod

How it starts

Implementation Plan

Initial Response

Process Steps

Step 1: Context Gathering & Initial Analysis

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement