sdlc-phase-report

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

A command that turns the documents and other work products for a software-development phase into a self-contained HTML report for stakeholders to read in a browser.

In plain words
What is it for?
Use it to generate a report for the current phase, a specified phase, or all phases, including an index when reporting on the whole project.
Why use it?
It gathers phase information into a reviewable report instead of requiring people to inspect many project files individually.

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

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-phase-report
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-phase-report

README.md
[![agentmods](https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-phase-report.svg)](https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-phase-report)
Your own site
<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-phase-report"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-phase-report.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 826 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.00826
Opus 5 $0.00000 $0.00413
Sonnet 5 $0.00000 $0.00165
Haiku 4.5 $0.00000 $0.00083

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

Security

Grade A, and why

sdlc-phase-report 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 4d 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-phase-report.md · 72 lines

How it starts

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

/sdlc-phase-report — Generate Phase HTML Report

Render all artifacts for the current (or specified) phase into a self-contained HTML report for stakeholder review.

Instructions

  1. Locate state file: Look for .sdlc/state.yaml in the current project directory. If not found, tell the user to run /sdlc-setup first.

  2. Determine target phase:

    • No argument → use current_phase from state file
    • Phase-id argument (e.g., /sdlc-phase-report 2) → use that phase id
    • Validate the id against the registry (0, 1, 2, 3, build, 7, 8, 9, close)
  3. Run report generator:

    For a single phase:

    uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/generate_phase_report.py \
      --state .sdlc/state.yaml \
      --phase <phase-id>
    

    The output defaults to .sdlc/reports/<slug>-report.html, where <slug> is the phase's registry slug (e.g. 00-discovery-report.html, build-report.html); pass --output only to override it.

    For all phases (produces individual reports and index.html):

    uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/generate_phase_report.py \
      --state .sdlc/state.yaml \
      --all
    

    Where ${CLAUDE_PLUGIN_ROOT} is the environment variable Claude Code sets to the plugin's install directory.

  4. Handle output:

    • On success: automatically open the report in the user's default browser:
      start .sdlc/reports/<slug>-report.html    # Windows
      open .sdlc/reports/<slug>-report.html     # macOS
      xdg-open .sdlc/reports/<slug>-report.html # Linux
      
    • On failure: display the error from the script and suggest checking that artifact files exist
  5. Update project index: After generating the phase report, create or update .sdlc/reports/index.html:

    • If index.html does not exist: create it with project header, mission, constitution link, and all 9 phases (0, 1, 2, 3, build, 7, 8, 9, close) showing current status
    • If index.html exists: update the phase status badges, dates, and report links to reflect current state
    • The index is the single entry point for all project documentation

Read the full file on GitHub · 72 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. 4d ago First seen · 72 lines · 0 tokens per session scan A e9808d5ba108

Subscribe to this mod's changes

sdlc-phase-report 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 826 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.