A command that creates a PLANS.md file in a project’s main folder to organise planned work. It can use details from a GitHub issue, a service for tracking software tasks and discussions.

Use it to turn a project goal or GitHub issue into a structured execution plan with tasks, deliverables, and acceptance criteria.

It gives a project one shared place for goals, scope, milestones, progress, discoveries, and decisions. This reduces the need to reconstruct the plan from scattered notes and issue comments.

create-plan — Command by liam-hq

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 commands/liam-hq/liam/create-plan

Clone the repo

git clone --depth 1 https://github.com/liam-hq/liam

Made for: Claude Code.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00011	$0.00428
Opus 5	$0.00005	$0.00214
Sonnet 5	$0.00002	$0.00086
Haiku 4.5	$0.00001	$0.00043

Measured 2d ago against content hash 15d7f4a9ed60, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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/commands/create-plan.md · 79 lines

What it actually says

Task

Create a comprehensive PLANS.md file in the project root directory to track project execution.

Input Handling

If the arguments contain a GitHub issue reference:

Extract the issue number from arguments (format: #123, 123, or GitHub URL)
Use gh issue view <issue-number> to fetch the issue details
Understand the requirements and context from the issue
Search the codebase for relevant files if needed
Use the issue information to populate the PLANS.md sections

Structure

The PLANS.md should include these sections:

Purpose / Big Picture
- Project goal summary
- User benefits
- Expected user-visible behavior
Initial Requirements & Scope
- High-level requirements
- Key features list
- In-scope vs. out-of-scope items
Milestones & Deliverables
- Work phases breakdown
- Specific deliverables
- Acceptance criteria
Progress
- Checkbox task list for granular tracking
- Completion status
- Progress dates
Surprises & Discoveries
- Unexpected learnings
- Technical challenges
- New insights
Decision Log
- Key decisions with dates
- Reasoning and context
- Supporting references
Outcomes & Retrospectives
- Milestone results
- Lessons learned
- What went well / could improve

Guidelines

Start with information gathered from the current project context
Use the user's input to understand the project scope
Keep it concise but comprehensive
Format as a living document that can evolve
Use markdown checkboxes - [ ] for trackable tasks

Arguments

Accepts:

Project description or context (free text)
GitHub issue number (e.g., 123 or #123)
GitHub issue URL

$ARGUMENTS

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.

2d ago First seen · 79 lines · 11 tokens per session scan A 15d7f4a9ed60

Subscribe to this mod's changes

create-plan is a command published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 4d ago), licensed Apache-2.0. It adds 11 tokens to every session and 428 once invoked, about $0.0001 per session on Opus 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.

Planning Project management data-visualization database-schema documentation documentation-tool entity-relationship-diagram

create-plan

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Task

Input Handling

Structure

Guidelines

Arguments

What this file has done since we first saw it

Other commands, from other repositories

github-sync

abandon

overview

status

ado-pull

archive