agentmods.dev

sdlc-revise

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

A command for changing one identified project artifact—such as a requirement or business rule—instead of rewriting an entire document. It records the reason, routes the change to the responsible discipline, and checks its effects again.

In plain words
What is it for?
Use it to revise an artifact by its ID or document section, record who requested the change and why, re-run project checks, and review what has been put at risk.
Why use it?
It keeps revisions focused and traceable, while making the owner and consequences of a change visible. A human must approve the proposed change.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-revise.svg)](https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-revise)
Your own site
<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-revise"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-revise.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,980 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.01980
Opus 5 $0.00000 $0.00990
Sonnet 5 $0.00000 $0.00396
Haiku 4.5 $0.00000 $0.00198

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

Security

Grade A, and why

sdlc-revise 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-revise.md · 136 lines

How it starts

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

/sdlc-revise — Change One Specific Artifact (and record why)

Adjust a thing, not a whole file. Artifacts already carry ids, so you revise FR-012 or BR-04 or one section — the command routes the change to the discipline that owns it, records the why with an owner and a clock, re-gates, and shows you exactly what the change put at risk.

/sdlc-revise FR-012
/sdlc-revise BR-04
/sdlc-revise requirements.md#non-functional-requirements

The One Rule holds throughout: the discipline agent proposes the change; a named human decides it. No agent silently rewrites an artifact.

Instructions

  1. Resolve mode and repo root:

    • Workflow mode (default): look for .sdlc/state.yaml; pass --state .sdlc/state.yaml to the scripts. If not found, tell the user to run /sdlc-setup first.
    • Standalone mode (--repo <path>, or no .sdlc/): operate on the given repo. Note the missing engagement context in the change reason.

  2. Resolve the target — id first, heading fallback.

    • If the argument is an id (FR-012, BR-04, EP-3, US-007, SCEN-02, FE-01, ADR-004), find the artifact that declares it.
    • If it is file.md#heading-slug, resolve to that file and section.
    • If it is a bare file, ask which section/id inside it the user means.
    • If ambiguous, ask (AskUserQuestion) — never guess which artifact.

  3. Preview the blast radius before you change anything:

    uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/audit_artifacts.py impact <target> --state .sdlc/state.yaml

    Show the human what depends on this target (declared vs. coarse) so they revise with eyes open.

  4. Interview to change it — route to the owning discipline agent. The agent proposes concrete wording; the human confirms or edits.

    Before applying the confirmed edit, snapshot the pre-image (advisory, exit 0) so the change is reversible — this captures the artifact's current content into the local version store lockstep with the ledger:

    uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/audit_artifacts.py record --scan --state .sdlc/state.yaml

    Then apply the confirmed edit to the artifact file. (Step 5a's record --event revised then captures the post-image, so /sdlc-version diff/rollback sees both sides of the change.) Content capture is best-effort; if the store can't be written the ledger append is byte-identical.

Read the full file on GitHub · 136 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 · 136 lines · 0 tokens per session scan A 16173c325c08

Subscribe to this mod's changes

sdlc-revise 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,980 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.

Planning
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

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

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