ai-prd-workflow: Command for Claude Code

.claude/commands/workflow-status.md

workflow-status is a command for Claude Code from nurettincoban/ai-prd-workflow. It costs 10 tokens per session (751 once invoked), scanned A, original, MIT.

A status command for an RFC-driven development workflow, where written project decisions guide implementation. It checks which documents and review records exist.

In plain words
What is it for?
Use it to check for documents such as a product requirements document, feature list, rules, RFCs, testing strategy, implementation reviews, and change requests, then choose the next stage.
Why use it?
It shows how far the project has progressed and prevents the next work step from being unclear.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is nurettincoban/ai-prd-workflow's own configuration. It tells Claude Code how to work on ai-prd-workflow 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 ai-prd-workflow configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nurettincoban/ai-prd-workflow. 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/nurettincoban/ai-prd-workflow/main/.claude/commands/workflow-status.md
Clone the repo
git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow

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 workflow-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/workflow-status.svg)](https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/workflow-status)
Your own site
<a href="https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/workflow-status"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/workflow-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 751 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.00010 $0.00751
Opus 5 $0.00005 $0.00376
Sonnet 5 $0.00002 $0.00150
Haiku 4.5 $0.00001 $0.00075

Measured 8d ago against content hash 5bfa784f9389, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

workflow-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 8d 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/workflow-status.md · 46 lines

What it actually says

You are guiding a project through an RFC-driven development workflow with these stages:

# Stage Artifact Command / Prompt
1 Create PRD PRD.md /create-prd (interactive-prd-creation-prompt.md)
2 Verify PRD PRD.md (improved) + PRD-REVIEW.md /verify-prd (prd-comprehensive-verification-prompt.md)
3 Extract features FEATURES.md /extract-features (prd-to-features-prompt.md)
4 Generate rules RULES.md /generate-rules (prd-to-rules-prompt.md)
5 Generate RFCs RFCs/ folder + RFCS.md /generate-rfcs (prd-to-rfcs-prompt.md)
6 Testing strategy TEST-STRATEGY.md /test-strategy (testing-strategy-prompt.md)
7 Implement RFCs (one by one, in order) Code /implement-rfc <id> (implementation-prompt-template.md)
8 Review each implementation reviews/REVIEW-RFC-<id>.md /review-rfc <id> (code-review-prompt.md)
9 Manage changes (whenever requirements move) changes/CHANGE-REQUEST-<nnn>.md /manage-changes (prd-change-management-prompt.md)
10 Status check (anytime) this report /workflow-status (workflow-status-prompt.md)

Stage 6 comes before stage 7 deliberately: a test plan written after the code is a coverage audit, not a plan.

Inspect the current project to determine workflow progress:

  1. Which artifacts exist: PRD.md, PRD-REVIEW.md, FEATURES.md, RULES.md, RFCS.md, RFCs/ folder, reviews/, changes/?
  2. Which RFCs appear implemented in the codebase versus not yet started? Compare each RFC's acceptance criteria against the actual code — do not assume an RFC is done just because code exists.
  3. Which RFCs have been reviewed? Check reviews/ for a report per implemented RFC — an implemented RFC with no review is the most common real-world gap, and reviews are exactly what gets skipped under deadline.
  4. Are there open change requests in changes/ whose decisions are still pending?
  5. Any signs of drift: code that contradicts the PRD or RULES.md, features in the codebase with no RFC, RFCs skipped out of order?

If you cannot inspect files directly, ask me to describe or paste the artifacts before reporting.

Then report:

  1. Status table — each workflow stage with its artifact and status (Done / In progress / Missing / Stale)

  2. Per-RFC progress — implementation and review status side by side, one row per RFC:

    RFC-001  implemented ✅   reviewed ❌
    RFC-002  implemented ✅   reviewed ❌
    RFC-003  implemented ✅   reviewed ✅
    

    A single "reviews done" row hides which RFCs were actually reviewed. Report them individually.

  3. Inconsistencies — anything drifted, skipped, or contradictory, with file references

  4. Next step — the single recommended next action, with the exact command or prompt to run

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. 8d ago First seen · 46 lines · 10 tokens per session scan A 5bfa784f9389

Subscribe to this mod's changes

workflow-status is a command published in the GitHub repository nurettincoban/ai-prd-workflow (284 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 751 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.