What is feature-plan?

A command that turns a short feature request into a structured feature-plan document. It follows the project's documentation location, naming rules, and template when those are available.

Use it to create or update feature plans, record unknowns as TBD, and keep sections such as current work, feature history, and next steps concise.

It removes the need to decide where a plan belongs or how it should be structured. It also helps update an existing plan without overwriting its current work.

feature-plan — Command by MedAdemBHA

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/medadembha/docflow/feature-plan

Clone the repo

git clone --depth 1 https://github.com/MedAdemBHA/docflow

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

When invoked 722 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.00015	$0.00722
Opus 5	$0.00008	$0.00361
Sonnet 5	$0.00003	$0.00144
Haiku 4.5	$0.00002	$0.00072

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

Security

Grade A, and why

feature-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.

commands/feature-plan.md · 93 lines

How it starts

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

Follow this prompt spec to create a docflow feature plan from this request:

$ARGUMENTS

Rules

If the request is empty, ask for one short feature description and stop.
Treat the request as the source brief, not as final truth. Infer sensible defaults, and mark unknowns as TBD.
Create or update one plan file under <DOCS_ROOT>/plans/features/.
Do not overwrite an existing feature plan blindly. If the target file exists, merge the new request into the existing In flight, Feature log, and Next sections.
Keep output lean: tables and bullets, no filler.

Steps

Find the docs root:
- Read docflow.json from $CLAUDE_PROJECT_DIR if present and use docsRoot.
- Otherwise use docs.
Read:
- <DOCS_ROOT>/README.md
- <DOCS_ROOT>/NAMING.md
- ${CLAUDE_PLUGIN_ROOT}/templates/plans/features/(mmm-yy)-feature-name.md
Derive:
- feature name from $ARGUMENTS
- kebab-case slug
- month prefix from the current date: (mmm-yy)
- target path: <DOCS_ROOT>/plans/features/(mmm-yy)-<slug>.md

Write the plan using this shape:

# Feature — <Name>

> **Status (<YYYY-MM-DD>):** proposed
> **Owner:** TBD
> **Surface:** `<code path or TBD>`

<2-3 lines: scope, users, current goal.>

Reference docs:
- Product: TBD
- Spec: TBD

Decisions:
- TBD

## In flight

| Item | Status |
|------|--------|
| <item> | proposed |

## Feature log

| Date | Change | Ref |
|------|--------|-----|
| <YYYY-MM-DD> | Created feature plan from request: `<short request>` | `/docflow:feature-plan` |

## Next

1. <next step>

If the request changes product behavior, note that product-spec/ should be updated.
If the request implies implementation architecture, note that specs/ should be updated.

Regenerate the docs map:

bash "$CLAUDE_PROJECT_DIR/scripts/docflow-map.sh" "$CLAUDE_PROJECT_DIR/$DOCS_ROOT"

If the target repo does not have scripts/docflow-map.sh, use:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/docflow-map.sh" "$CLAUDE_PROJECT_DIR/$DOCS_ROOT"

Run link check if available:

bash "$CLAUDE_PROJECT_DIR/scripts/check-links.sh" "$CLAUDE_PROJECT_DIR/$DOCS_ROOT"

Run validation if available:

bash "$CLAUDE_PROJECT_DIR/scripts/docflow-validate.sh" --target "$CLAUDE_PROJECT_DIR"

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

2d ago First seen · 93 lines · 15 tokens per session scan A 3366525a1155

Subscribe to this mod's changes

feature-plan is a command published in the GitHub repository MedAdemBHA/docflow (41 stars, last pushed 18d ago), licensed MIT. It adds 15 tokens to every session and 722 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 Writing and docs ai-agents claude-code-plugin codex-plugin documentation

feature-plan

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Rules

Steps

What this file has done since we first saw it

Other commands, from other repositories

search

review-renovate

monitor-ci

ado-pull

github-push

export