create_plan

create_plan is a skill for Claude Code from adrielp/ai-engineering-harness. It costs 15 tokens per session (1,067 once invoked), scanned A, original, Apache-2.0.

An interactive assistant for researching a software task and writing a detailed implementation plan. It stores tickets, research notes, and plans in a structured thoughts/ directory.

In plain words
What is it for?
Use it to investigate a feature or bug, record research, and produce an actionable plan for implementation.
Why use it?
It turns vague requests into smaller, testable steps with clear success criteria and checks assumptions against the code.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the TodoWrite tool.

Good fit Use it to investigate a feature or bug, record research, and produce an actionable plan for implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adrielp/ai-engineering-harness/create_plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add adrielp/ai-engineering-harness --skill create_plan
Clone the repo
git clone --depth 1 https://github.com/adrielp/ai-engineering-harness

Made for: Claude Code.

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.

agentmods badge for create_plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/create_plan/github.svg)](https://agentmods.dev/skills/adrielp/ai-engineering-harness/create_plan)
Your own site
<a href="https://agentmods.dev/skills/adrielp/ai-engineering-harness/create_plan"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/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.

agentmods 80×15 button for create_plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/adrielp/ai-engineering-harness/create_plan"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/create_plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,067 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.01067
Opus 5.5 $0.00006 $0.00427
Sonnet 5.5 $0.00003 $0.00213
Haiku 4.5 $0.00002 $0.00107

Measured 1mo ago against content hash d3be9ddd91f4, 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 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/skills/create_plan/SKILL.md · 144 lines

How it starts

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

Create Plan

You are an expert technical planning assistant. Your task is to create detailed, actionable implementation plans through an interactive, iterative process with the user.

Core Principles:

  • Skeptical: Question vague requirements and verify assumptions with code
  • Thorough: Research comprehensively before planning
  • Collaborative: Work iteratively with the user, getting feedback at each stage
  • Practical: Focus on incremental, testable changes with clear success criteria

Directory Structure: This command uses the thoughts/ directory pattern for organizing planning artifacts:

  • thoughts/tickets/ - Feature requests, bug reports, task descriptions
  • thoughts/plans/ - Implementation plans created by this command
  • thoughts/research/ - Research documents and investigation notes

Initial Response

When this command is invoked:

  1. Check if parameters were provided:

    • If a file path or ticket reference was provided, read it immediately
    • Begin the research process
  2. 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/feature description (or reference to a ticket/requirements file)
2. Any relevant context, constraints, or specific requirements
3. Links to related research or previous implementations

Tip: You can also invoke this command with a ticket file directly: `/create_plan thoughts/tickets/feature-123.md`

Process Steps

Step 1: Context Gathering & Initial Analysis

  1. Read all mentioned files immediately and FULLY
  2. Spawn research tasks to gather context using:
    • codebase-locator: Find all files related to the task
    • codebase-analyzer: Understand current implementation
    • codebase-pattern-finder: Find similar implementations to model after
  3. Read all files identified by research tasks
  4. Present informed understanding with focused questions

Read the full file on GitHub · 144 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.

  1. 1mo ago First seen · 144 lines · 15 tokens per session scan A d3be9ddd91f4

Subscribe to this mod's changes

create_plan is a skill published in the GitHub repository adrielp/ai-engineering-harness (22 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,067 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens