agentmods.dev

spec-review

A command that checks a feature specification against a review checklist and records whether it passes.

In plain words
What is it for?
Use it to review a specification, check that each acceptance criterion can be tested independently, and produce a list of required edits.
Why use it?
It finds missing, unclear, or untestable requirements before implementation begins, so review does not rely on memory or guesswork.

Command for Claude Code

58 +1 2mo ago A scan 19 tokens original MIT
View the source file loiane/specs-driven-development-spring-angular
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/loiane/specs-driven-development-spring-angular/spec-review
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 398 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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00398
Opus 5 $0.00010 $0.00199
Sonnet 5 $0.00004 $0.00080
Haiku 4.5 $0.00002 $0.00040

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

Security

Grade A, and why

spec-review 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.

.claude/commands/spec-review.md · 40 lines

What it actually says

/spec-review

Phase: 2 — review Owning agent: .claude/agents/spec-author.md (review hat) Skills used: ears-spec-authoring, requirements-traceability

Purpose

Audit 01-spec.md against the spec checklist and produce 02-spec-review.md with a pass/fail verdict and a numbered list of required edits.

Inputs

  • <feature-id> (positional). If omitted, use the most recently modified .specs/<id>/.

Reads

  • .specs/<feature-id>/01-spec.md
  • .claude/checklists/spec-review.md
  • .claude/templates/spec-review.template.md

Writes

  • .specs/<feature-id>/02-spec-review.md

Process

  1. Walk every checklist item; for each, record pass | fail | n/a plus a one-line rationale.
  2. For each fail, write a concrete edit (line + replacement) the spec author must apply.
  3. Verify EARS form compliance for every AC.
  4. Verify each AC is independently testable (no compound criteria).
  5. Verify ## Open Questions is empty before declaring overall verdict PASS.
  6. Emit summary: verdict, acs_total, acs_failed, open_questions, next_command.

Refuse if

  • 01-spec.md does not exist.
  • Any Q-NNN is unresolved — verdict must be FAIL with the open question list quoted verbatim.

Done when

02-spec-review.md exists. If verdict is PASS, point the user to /plan. If FAIL, point them back to editing 01-spec.md.

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. 2d ago First seen · 40 lines · 19 tokens per session scan A 595470d04498

Subscribe to this mod's changes

spec-review is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 398 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.

Code reviewangulargithub-copilotspec-driven-developmentspring-boot
Related

Other commands, from other repositories

spec-kitty-standalone

This host should read Spec Kitty's canonical standalone-invocation skill pack at.

Priivacy-ai/spec-kitty · 0 tokens

spec-kitty.analyze

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

Priivacy-ai/spec-kitty · 0 tokens

my-own-prompt

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

Priivacy-ai/spec-kitty · 0 tokens

sdd-featherspec-update

Check the installed FeatherSpec version and update safely — fetch a release, migrate, preserve customizations. Resumable.

GregorBiswanger/featherspec · 24 tokens

sdd-plan

Turn a spec into a persisted baby-step plan file — research, resume, impact analysis.

GregorBiswanger/featherspec · 18 tokens

sdd-clean

Context cleanup — analyze FeatherSpec's persistent markdown, dedupe and compact safely, with a token report.

GregorBiswanger/featherspec · 21 tokens