What is plan-writing?

A structured way to plan coding work before implementation. It breaks a feature or refactor into small tasks with dependencies and checks for confirming completion.

Use it to plan features, refactors, and other multi-step changes, including the tests or checks needed to verify the result.

It reduces uncertainty about what to do next and helps prevent missed steps. It also keeps multi-step plans short and ordered.

plan-writing — Skill by diillson

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.

agentmods

npx agentmods add skills/diillson/chatcli/plan-writing

Any agent

npx skills add diillson/chatcli --skill plan-writing

Clone the repo

git clone --depth 1 https://github.com/diillson/chatcli

Made for: Claude Code, Codex.

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

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

Security scan A 1 finding. Scan, not verified.

Origin 95% 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	$0.00031	$0.01019
Opus 5	$0.00015	$0.00509
Sonnet 5	$0.00006	$0.00204
Haiku 4.5	$0.00003	$0.00102

Measured 3d ago against content hash 93cd02ab3c43, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-writing 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 3d 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.

| "Test the API" | "curl localhost:3000/api/users returns 200" |

Origin

This is a copy

95% identical to plan-writing — 11 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.

.agent/skills/plan-writing/SKILL.md · 153 lines

How it starts

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

Plan Writing

Source: obra/superpowers

Overview

This skill provides a framework for breaking down work into clear, actionable tasks with verification criteria.

Task Breakdown Principles

1. Small, Focused Tasks

Each task should take 2-5 minutes
One clear outcome per task
Independently verifiable

2. Clear Verification

How do you know it's done?
What can you check/test?
What's the expected output?

3. Logical Ordering

Dependencies identified
Parallel work where possible
Critical path highlighted
Phase X: Verification is always LAST

4. Dynamic Naming in Project Root

Plan files are saved as {task-slug}.md in the PROJECT ROOT
Name derived from task (e.g., "add auth" → auth-feature.md)
NEVER inside .claude/, docs/, or temp folders

Planning Principles (NOT Templates!)

🔴 NO fixed templates. Each plan is UNIQUE to the task.

Principle 1: Keep It SHORT

❌ Wrong	✅ Right
50 tasks with sub-sub-tasks	5-10 clear tasks max
Every micro-step listed	Only actionable items
Verbose descriptions	One-line per task

Rule: If plan is longer than 1 page, it's too long. Simplify.

Principle 2: Be SPECIFIC, Not Generic

❌ Wrong	✅ Right
"Set up project"	"Run `npx create-next-app`"
"Add authentication"	"Install next-auth, create `/api/auth/[...nextauth].ts`"
"Style the UI"	"Add Tailwind classes to `Header.tsx`"

Rule: Each task should have a clear, verifiable outcome.

Principle 3: Dynamic Content Based on Project Type

For NEW PROJECT:

What tech stack? (decide first)
What's the MVP? (minimal features)
What's the file structure?

For FEATURE ADDITION:

Which files are affected?
What dependencies needed?
How to verify it works?

For BUG FIX:

What's the root cause?
What file/line to change?
How to test the fix?

Principle 4: Scripts Are Project-Specific

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

3d ago First seen · 153 lines · 31 tokens per session scan A 93cd02ab3c43

Subscribe to this mod's changes

plan-writing is a skill published in the GitHub repository diillson/chatcli (89 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,019 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 95% identical to plan-writing, differing in 11 lines, and is treated as a copy.

Planning agent ai aiops compression context-engineering context-window

plan-writing