Borrowing it
Nothing to install: this file belongs to Caspian-Sun/claude-code-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.
curl -O https://raw.githubusercontent.com/Caspian-Sun/claude-code-workflow/main/.claude/commands/prd-check.mdgit clone --depth 1 https://github.com/Caspian-Sun/claude-code-workflowWrote 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.
[](https://agentmods.dev/commands/caspian-sun/claude-code-workflow/prd-check)<a href="https://agentmods.dev/commands/caspian-sun/claude-code-workflow/prd-check"><img src="https://agentmods.dev/badge/commands/caspian-sun/claude-code-workflow/prd-check/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.
<a href="https://agentmods.dev/commands/caspian-sun/claude-code-workflow/prd-check"><img src="https://agentmods.dev/badge/commands/caspian-sun/claude-code-workflow/prd-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01934 |
| Opus 5.5 | $0.00000 | $0.00774 |
| Sonnet 5.5 | $0.00000 | $0.00387 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
prd-check 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are now a PRD completeness checker. Run hard-gate checks against the input PRD file and output whether it can proceed to the /plan task breakdown phase.
Applicable Scenarios
- User self-checks during PRD review — make a change and run immediately to know how far from "ready to run
/plan" - Mandatory pre-check for
/plan—/planmust run this command first; if it fails, task breakdown is refused
Input
@docs/prds/xxx.mdpath → read directly- No path → stop and ask: "Please specify the PRD file path, e.g.: /prd-check @docs/prds/login.md"
Checks (run in order, no short-circuit — report all issues at once)
Run all 5 checks in sequence, collect all results before summarizing. Do not stop at the first failure — users want to see all issues at once.
Check 1: Zero [TBD] hits (P0, must pass)
Full-text grep for [TBD]; hit count must be 0.
- Why strict:
[TBD]will propagate all the way totask.businessRules→ source file@rules→ testit()assertions — everything downstream becomes wrong. Blocking at the entry point has the lowest cost. - On failure: list the line number and text snippet for each hit
Check 2: Zero [TBD] hits in body text (P1)
Full-text grep for [TBD]. Allowed in:
- Metadata table ("Owner" field)
- Change log table ("Changed by" column)
Not allowed anywhere else in the document body.
- Why the metadata exception: these fields are collaboration info and don't affect downstream generation
- On failure: list the out-of-bounds hit locations
Check 3: Business Rules section contains no placeholders (P0)
Scan all entries under ### Business Rules sections; each entry must not contain:
-
[TBD] -
TODO/FIXME/??? -
Empty entries (e.g.,
1.) -
Why strict:
businessRulesis the direct source for task breakdown and test generation — placeholders mean downstream assertions are unreliable -
On failure: identify which feature point and which rule contains the placeholder
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.
- 2mo ago First seen · 188 lines · 0 tokens per session scan A fdfe2de29f5d
prd-check is a command published in the GitHub repository Caspian-Sun/claude-code-workflow (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,934 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.
Other commands, from other repositories
coverage
Verify every MDX file in docs/ is tracked in contributing/INDEX.md.
report
Professional report command. Turns raw data and findings into professional, audience-appropriate reports.
docs-audit
Documentation audit command. Evaluates completeness, freshness, and quality of technical documentation.
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
brand-generate
Generate an on-brand document from a saved Brand Profile.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.