aidlc: Command for Claude Code

.claude/commands/plan.md

plan is a command for Claude Code from aidlc-io/aidlc. It costs 25 tokens per session (325 once invoked), scanned A, original, MIT.

A planning command for an epic, meaning a large piece of product work made up of smaller tasks. It reads the project's workflow configuration and creates a product requirements document for the planning phase.

In plain words
What is it for?
Use it to start the configured planning phase for an epic, load its assigned instructions, read the required inputs, and write the resulting PRD to the project's documentation.
Why use it?
It turns an approved work item into a documented plan that later development phases can use.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

This is aidlc-io/aidlc's own configuration. It tells Claude Code how to work on aidlc itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aidlc configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aidlc-io/aidlc. 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/aidlc-io/aidlc/main/.claude/commands/plan.md
Clone the repo
git clone --depth 1 https://github.com/aidlc-io/aidlc

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 plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/aidlc-io/aidlc/plan/github.svg)](https://agentmods.dev/commands/aidlc-io/aidlc/plan)
Your own site
<a href="https://agentmods.dev/commands/aidlc-io/aidlc/plan"><img src="https://agentmods.dev/badge/commands/aidlc-io/aidlc/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 plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/aidlc-io/aidlc/plan"><img src="https://agentmods.dev/badge/commands/aidlc-io/aidlc/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 325 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.00025 $0.00325
Opus 5.5 $0.00010 $0.00130
Sonnet 5.5 $0.00005 $0.00065
Haiku 4.5 $0.00003 $0.00032

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

Security

Grade A, and why

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 2mo 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/plan.md · 24 lines

What it actually says

/plan — Plan

You were invoked as /plan <epic> with arguments: $ARGUMENTS (the epic id).

Run the plan phase for this epic by following the AIDLC dispatch procedure exactly as /aidlc <epic> plan would:

  1. Read docs/epics/<epic>/state.json → pipelineId.
  2. In .aidlc/workspace.yaml, find that pipeline and its plan step (name/agent === plan). Use that step's agent + skills — never assume; two pipelines can wire plan differently.
  3. If the pipeline has no plan step, tell the user this epic's pipeline (<pipelineId>) has no plan phase, suggest /aidlc <epic> to run the next eligible phase, and stop.
  4. Otherwise load the persona (.claude/agents/<agent>.md) + skill(s) (.claude/skills/<skill>.md), adopt them (unless the active standard is none), then follow the structural contract: read state/inputs, write to docs/epics/<epic>/artifacts/PRD.md (or the step's declared artifact), and tell the user to click "Mark step done".
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. 2mo ago First seen · 24 lines · 0 tokens per session scan A 17f02c7a6dca

Subscribe to this mod's changes

plan is a command published in the GitHub repository aidlc-io/aidlc (65 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 325 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.