What is create-plans?

A guide for making project plans that a coding agent can execute and verify. It breaks work into small, focused plans with clear tasks and checks instead of one large document.

Use it to turn a brief into phases and small plans, define verification criteria, create roadmaps, and prepare context handoffs.

It reduces context overload and makes each stage easier to implement, review, and hand to the next stage.

create-plans — Skill for Claude Code by Vibe-Marketer

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 Vibe-Marketer/plugins-and-skills --skill create-plans

Clone the repo

git clone --depth 1 https://github.com/Vibe-Marketer/plugins-and-skills

Made for: Claude Code.

Or install dev-toolkit, the plugin that ships this one along with the rest of its 9 skills.

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/skills/vibe-marketer/plugins-and-skills/create-plans.svg)](https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/create-plans)

Your own site

<a href="https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/create-plans"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-skills/create-plans.svg" alt="Measured on agentmods" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

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

Origin 100% copy Near-identical to another mod 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.00057	$0.04396
Opus 5	$0.00028	$0.02198
Sonnet 5	$0.00011	$0.00879
Haiku 4.5	$0.00006	$0.00440

Measured 7d ago against content hash c0adb5d8a791, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

create-plans scanned grade B 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 7d 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

ls ~/.claude/skills/expertise/ 2>/dev/null

Origin

This is a copy

100% identical to create-plans — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

dev-toolkit/skills/create-plans/SKILL.md · 489 lines

How it starts

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

<essential_principles>

When planning a phase, you are writing the prompt that will execute it.

The quality degradation curve:

0-30% context: Peak quality (comprehensive, thorough, no anxiety)
30-50% context: Good quality (engaged, manageable pressure)
50-70% context: Degrading quality (efficiency mode, compression)
70%+ context: Poor quality (self-lobotomization, rushed work)

Critical insight: Claude doesn't degrade at 80% - it degrades at ~40-50% when it sees context mounting and enters "completion mode." By 80%, quality has already crashed.

Solution: Aggressive atomicity - split phases into many small, focused plans.

Examples:

01-01-PLAN.md - Phase 1, Plan 1 (2-3 tasks: database schema only)
01-02-PLAN.md - Phase 1, Plan 2 (2-3 tasks: database client setup)
01-03-PLAN.md - Phase 1, Plan 3 (2-3 tasks: API routes)
01-04-PLAN.md - Phase 1, Plan 4 (2-3 tasks: UI components)

Each plan is independently executable, verifiable, and scoped to 2-3 tasks maximum.

Atomic task principle: Better to have 10 small, high-quality plans than 3 large, degraded plans. Each commit should be surgical, focused, and maintainable.

Autonomous execution: Plans without checkpoints execute via subagent with fresh context - impossible to degrade.

See: references/scope-estimation.md

Checkpoint types:

checkpoint:human-verify - Human confirms Claude's automated work (visual checks, UI verification)
checkpoint:decision - Human makes implementation choice (auth provider, architecture)

Rarely needed: checkpoint:human-action - Only for actions with no CLI/API (email verification links, account approvals requiring web login with 2FA)

Critical rule: If Claude CAN do it via CLI/API/tool, Claude MUST do it. Never ask human to:

Deploy to Vercel/Railway/Fly (use CLI)
Create Stripe webhooks (use CLI/API)
Run builds/tests (use Bash)
Write .env files (use Write tool)
Create database resources (use provider CLI)

Protocol: Claude automates work → reaches checkpoint:human-verify → presents what was done → waits for confirmation → resumes

See: references/checkpoints.md, references/cli-automation.md

During execution, deviations are handled automatically via 5 embedded rules:

Auto-fix bugs - Broken behavior → fix immediately, document in Summary
Auto-add missing critical - Security/correctness gaps → add immediately, document
Auto-fix blockers - Can't proceed → fix immediately, document
Ask about architectural - Major structural changes → stop and ask user
Log enhancements - Nice-to-haves → auto-log to ISSUES.md, continue

No user intervention needed for Rules 1-3, 5. Only Rule 4 (architectural) requires user decision.

All deviations documented in Summary with: what was found, what rule applied, what was done, commit hash.

Result: Flow never breaks. Bugs get fixed. Scope stays controlled. Complete transparency.

Read the full file on GitHub · 489 lines

Files

What ships with it

31 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

7d ago First seen · 489 lines · 57 tokens per session scan B c0adb5d8a791

Subscribe to this mod's changes

create-plans is a skill published in the GitHub repository Vibe-Marketer/plugins-and-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 4,396 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). It is 100% identical to create-plans, differing in 0 lines, and is treated as a copy.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens

create-plans