context-driven-documentation: Command for Claude Code

.claude/commands/plan.md

plan is a command for Claude Code from guilhermegouw/context-driven-documentation. It costs 0 tokens per session (5,972 once invoked), scanned A, original, MIT.

A command that creates an implementation plan from project specifications. It follows the language configured in .cdd/config.yaml, using English by default when no language is set.

In plain words
What is it for?
Use it to turn specifications into a plan.md file. The available details do not explain the plan's exact sections or how implementation is carried out.
Why use it?
It gives development work a written plan before implementation begins. It also keeps the plan in the project's configured language.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is guilhermegouw/context-driven-documentation's own configuration. It tells Claude Code how to work on context-driven-documentation 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 context-driven-documentation configures β†’

Reuse

Borrowing it

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

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/guilhermegouw/context-driven-documentation/plan/github.svg)](https://agentmods.dev/commands/guilhermegouw/context-driven-documentation/plan)
Your own site
<a href="https://agentmods.dev/commands/guilhermegouw/context-driven-documentation/plan"><img src="https://agentmods.dev/badge/commands/guilhermegouw/context-driven-documentation/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/guilhermegouw/context-driven-documentation/plan"><img src="https://agentmods.dev/badge/commands/guilhermegouw/context-driven-documentation/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,972 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.00000 $0.05972
Opus 5.5 $0.00000 $0.02389
Sonnet 5.5 $0.00000 $0.01194
Haiku 4.5 $0.00000 $0.00597

Measured 2mo ago against content hash 849701ade546, 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 Β· 955 lines

How it starts

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


description: Autonomous implementation planning from specifications allowed-tools: Bash(cat:*)

🌍 Project Language Configuration

Detecting configured language from .cdd/config.yaml:

!cat .cdd/config.yaml | grep "language:" || echo "language: en"


CRITICAL STARTUP LANGUAGE RULE

Look at the language configuration detected above:

  • βœ… If you see language: pt-br β†’ START your FIRST message in Portuguese (PT-BR)
  • βœ… If you see language: en β†’ START your FIRST message in English

Examples of correct startup:

When config shows language: pt-br:

πŸ“‹ Entendi! Vou criar o plano de implementaΓ§Γ£o...

When config shows language: en:

πŸ“‹ Got it! I'll create the implementation plan...

LANGUAGE MATCHING RULE (After Startup)

After your first message: Always respond in the same language the user writes to you.

Behavior:

  • If user writes in English β†’ Continue in English
  • If user writes in Portuguese (PT-BR) β†’ Continue in Portuguese
  • User can switch languages mid-conversation, and you adapt

When generating file content (plan.md): Always use the template language that matches the .cdd/config.yaml language setting, regardless of what language the conversation is in.

Key Points:

  • First message: Use language from config.yaml
  • Conversation: Match user's language dynamically
  • Generated files: Always use language from config.yaml

Read the full file on GitHub Β· 955 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. 2mo ago First seen Β· 955 lines Β· 0 tokens per session scan A 849701ade546

Subscribe to this mod's changes

plan is a command published in the GitHub repository guilhermegouw/context-driven-documentation (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,972 tokens. 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-31.

Related

plan compared with commands from other repositories

plan next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
planguilhermegouw/context-driven-documentationCommand51y agoMITA0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
speckit.bug.testgithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code