A command that shows the current progress of a software project’s SDLC, or software development life cycle. It reads the project’s state file and displays the current phase, completed work, artifacts, timestamps, history, and specification counts by delivery channel.

Use it to check the active development phase, phase completion, generated artifacts, recent transitions, and the backlog of specifications across delivery channels.

It gives the team one view of where the project stands instead of requiring them to inspect state files and progress records manually. It also points out when the project has not been set up yet.

sdlc-status — Command for coding agents by MCKRUZ: A command that shows the current progress of a…

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

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-status.svg)](https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-status)

Your own site

<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-status"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-status.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 995 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00995
Opus 5	$0.00000	$0.00498
Sonnet 5	$0.00000	$0.00199
Haiku 4.5	$0.00000	$0.00100

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

Security

Grade A, and why

sdlc-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 3d 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-status.md · 71 lines

How it starts

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

/sdlc-status — SDLC Progress Dashboard

Display the current SDLC progress for this project.

Instructions

Locate state file: Look for .sdlc/state.yaml in the current project directory. If not found, tell the user to run /sdlc-setup first.
Read state: Load .sdlc/state.yaml to get current phase, phase statuses, and history.

Generate dashboard: Run the status generator:

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

Display: Show the generated dashboard to the user. Include:
- Current phase name and number
- Progress bar (completed phases / total)
- Phase table with status, artifact count, timestamps
- Recent transition history (if any)
Channel rollup + decision-log: Two additive reads that surface the multi-discipline layer without touching generate_status.py:
- By-channel spec backlog — derive the per-channel rollup from spec frontmatter:
```
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/track_specs.py --state .sdlc/state.yaml --json
```
  Render the by_channel block (spec counts per delivery surface; channel-agnostic and unassigned are first-class buckets). If the JSON has no by_channel key or every spec is unassigned, skip this — no project has bound a channel: yet.
- Open + overdue decisions — surface the phase-spanning decision-log:
```
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/track_decisions.py --state .sdlc/state.yaml --json
```
  List open decisions and flag those overdue past the 2-business-day clock (owner + due shown). If track_decisions.py or .sdlc/decision-log.md is absent, read .sdlc/decision-log.md directly for open items, or skip silently if neither exists. Advisory only (exit 0) — never blocks.
- Artifact staleness rollup — surface how many artifacts have drifted out of date with the things they depend on:
```
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/audit_artifacts.py report --state .sdlc/state.yaml --json
```
  If has_history is true, render one line — Artifacts: N stale (X acknowledged, Y open) — using stale, acknowledged, and open from the JSON. If has_history is false (no ledger yet) or the script is absent, skip silently — no baseline has been recorded. Advisory only (exit 0) — never blocks. See /sdlc-audit-artifacts for the full dashboard.

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

3d ago First seen · 71 lines · 0 tokens per session scan A c72a5ba43c86

Subscribe to this mod's changes

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

Project management

sdlc-status

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/sdlc-status — SDLC Progress Dashboard

Instructions

What this file has done since we first saw it

Other commands, from other repositories

project-recap

os-meeting

workspace

standup

m-task-planner

triage-issues