agentmods.dev

sdlc-review

sdlc-review is a command for coding agents from MCKRUZ/claude-code-sdlc. It costs 0 tokens per session (1,042 once invoked), scanned A, original, MIT.

A command that reviews the documents produced during the current software-development phase from several viewpoints, such as architecture, product, quality, security, design, data, and business needs.

In plain words
What is it for?
Use it to run a broad, skeptical, edge-case, or combined review of phase artifacts and produce a findings summary.
Why use it?
It brings different kinds of risks and overlooked assumptions into one review of the project’s current documents.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the claude-code-sdlc plugin — 9 skills, 28 commands, 20 agents shipped together

not rated 4 7d ago A scan 0 tokens original MIT
View the source file MCKRUZ/claude-code-sdlc
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/mckruz/claude-code-sdlc/sdlc-review
Clone the repo
git clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlc

Or install claude-code-sdlc, the plugin that ships this one along with the rest of its 9 skills, 28 commands, 20 agents.

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 sdlc-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-review.svg)](https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-review)
Your own site
<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-review"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,042 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.00000 $0.01042
Opus 5 $0.00000 $0.00521
Sonnet 5 $0.00000 $0.00208
Haiku 4.5 $0.00000 $0.00104

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

Security

Grade A, and why

sdlc-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 5d 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/sdlc-review.md · 84 lines

How it starts

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

/sdlc-review — Multi-Perspective Artifact Review

Run a structured review of the current phase's artifacts from multiple perspectives.

Instructions

  1. Read state: Load .sdlc/state.yaml to determine the current phase.

  2. Read artifacts: Load all artifacts in .sdlc/artifacts/{NN}-{phase-name}/.

  3. Determine mode from arguments:

    • --council (default) — 7-viewpoint review (Architecture, Product, Quality, Security, Design, Data, Bizreq)
    • --adversarial — Cynical QA perspective, challenge every assumption
    • --edge-cases — Exhaustive path analysis, find unhandled conditions
    • --all — Run all 3 modes sequentially, produce a combined report

  4. Spawn the multi-reviewer agent via the Agent tool:

    • Provide all artifact paths and the selected mode
    • Include profile context from .sdlc/profile.yaml for stack/quality awareness
    • Include frozen layers from .sdlc/context/layers/ for cross-phase context

  5. Display findings summary:

    Review Complete — Phase 2: Design (council mode)
================================================
CRITICAL: 0 | HIGH: 2 | MEDIUM: 4 | LOW: 1

Top findings:
1. [HIGH] No rollback strategy defined for database migration (Architecture)
2. [HIGH] Auth token refresh not specified for offline scenarios (Security)

Full report: .sdlc/artifacts/02-design/review-report.md

  6. Record the findings so they survive the next review (the report itself is overwritten each run):

    uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/record_findings.py record \
  --report .sdlc/artifacts/{NN}-{phase}/review-report.md --state .sdlc/state.yaml

    This parses the report's ## Gate Results block into the append-only ledger .sdlc/metrics/findings-log.jsonl, so a finding's disposition can be tracked across rounds and a recurring class of finding becomes visible over time. Then surface the standing picture:

    uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/record_findings.py report --state .sdlc/state.yaml

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

  1. 5d ago First seen · 84 lines · 0 tokens per session scan A 17d0743a61af

Subscribe to this mod's changes

sdlc-review is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,042 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.

Code reviewPlanning
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens