A project-status command that scans the documentation folder and reports the state of each of eight software-planning layers, including whether it exists, when it was edited, and whether it was reviewed.

Use it to check the progress of a project's BRD, PRD, EARS, BDD, ADR, SPEC, TDD, and IPLAN documents. These are common documents for requirements, design decisions, specifications, tests, and implementation planning.

It gives you one map of your planning progress instead of requiring you to inspect folders and review records yourself.

status — Command for Claude Code by vladm3105

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.

Clone the repo

git clone --depth 1 https://github.com/vladm3105/aidoc-flow-framework

Made for: Claude Code.

Or install aidoc-flow, the plugin that ships this one along with the rest of its 52 skills, 12 commands, 11 agents, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/status.svg)](https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/status)

Your own site

<a href="https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/status"><img src="https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/status.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 869 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.00869
Opus 5	$0.00010	$0.00434
Sonnet 5	$0.00004	$0.00174
Haiku 4.5	$0.00002	$0.00087

Measured 6d ago against content hash 2aed9c03cc1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

status 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 6d 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.

platforms/claude-code-plugin/commands/status.md · 85 lines

How it starts

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

Status

Answer the question "where am I in the 8-layer flow?" for the current project. Read the docs/ tree using the same docs/0N_<ARTIFACT>/ layout the PostToolUse hook (hooks/sdd-doc-review.sh) detects, plus the .aidoc/ scratch directory if present. Output is a per-layer table.

/aidoc-flow:next reads the same detection result and emits one concrete next action. Run /status to see the map; run /next to be told where to step.

Instructions

Resolve the project root — start from the current working directory. If .claude/aidoc-flow.config.yaml exists and sets docs_root, use that; otherwise default to docs/.

Scan the docs root for the eight canonical layer directories:

01_BRD  02_PRD  03_EARS  04_BDD  05_ADR  06_SPEC  07_TDD  08_IPLAN

For each layer, determine four facts:

Fact	How to determine
`exists`	The directory `<docs_root>/0N_<ARTIFACT>/` is present
`instances`	Count `.md` and `.yaml` files inside (excluding `00_index.*`)
`last_edit`	`git log -1 --format=%cs -- <dir>` if in a git repo, else `mtime` of the newest file
`audited`	An `.aidoc/<ARTIFACT>-NN.audit.*` (or equivalent project audit artifact) exists for at least one instance — heuristic; record `?` if unknown

Render the per-layer table:

Project: <cwd>
Docs root: <resolved docs_root>

| # | Layer | Exists | Instances | Last edit  | Audited |
|---|-------|--------|-----------|------------|---------|
| 1 | BRD   | yes    |         2 | 2026-06-12 | yes     |
| 2 | PRD   | yes    |         1 | 2026-06-13 | no      |
| 3 | EARS  | no     |           |            |         |
| … | …     | …      |           |            |         |
| 8 | IPLAN | no     |           |            |         |

Append a one-line summary — the position counted as "highest layer that exists":
```
Highest layer present: PRD (2 of 8). Latest edited: PRD on 2026-06-13.
```

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

6d ago First seen · 85 lines · 21 tokens per session scan A 2aed9c03cc1e

Subscribe to this mod's changes

status is a command published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 869 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-31.

Planning active workflow

context

A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.

fengshao1227/ccg-workflow · 23 tokens

spec-research

A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.

fengshao1227/ccg-workflow · 16 tokens

triage

Triage Linear issue with comprehensive analysis.

n8n-io/n8n · 7 tokens

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

sync

Manually trigger plan-sync to update downstream task specs after implementation drift.

gmickel/flow-next · 15 tokens

slack-gif-creator

Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".

hamr0/agentic-toolkit · 57 tokens