A command that runs a software development life cycle (SDLC)—the stages used to plan, build, check, release, and maintain software—in five phases with approval points between them.

Use it to coordinate feature work such as authentication or OAuth, rerun one phase, and organize planning, implementation, testing, security, release, and operations artifacts.

It keeps work from jumping straight from an idea to code and preserves handoff documents between phases.

sdlc — Command for Claude Code by saitarrun/Devforge-ai

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/saitarrun/Devforge-ai

agentmods

npx agentmods add commands/saitarrun/devforge-ai/sdlc

Made for: Claude Code.

Or install devforge-ai, the plugin that ships this one along with the rest of its 48 skills, 17 commands, 10 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/saitarrun/devforge-ai/sdlc/github.svg)](https://agentmods.dev/commands/saitarrun/devforge-ai/sdlc)

Your own site

<a href="https://agentmods.dev/commands/saitarrun/devforge-ai/sdlc"><img src="https://agentmods.dev/badge/commands/saitarrun/devforge-ai/sdlc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/saitarrun/devforge-ai/sdlc"><img src="https://agentmods.dev/badge/commands/saitarrun/devforge-ai/sdlc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 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,320 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00042	$0.01320
Opus 5.5	$0.00017	$0.00528
Sonnet 5.5	$0.00008	$0.00264
Haiku 4.5	$0.00004	$0.00132

Measured 1mo ago against content hash 36810237931a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sdlc 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 1mo 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.md · 115 lines

How it starts

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

Master SDLC Orchestrator

This command runs the complete Software Development Lifecycle end-to-end with 5 phases, explicit approval gates between each phase, and handoff documents to keep context windows bounded.

Usage

/sdlc "build a user authentication system"
/sdlc "add OAuth login" --from Plan --to Build
/sdlc --phase Build  # Re-run Build phase in isolation

Phases

The orchestrator runs agents sequentially across 5 phases:

Plan → /sdlc-plan (product-manager: grill interview + scope.json + PRD + issues)
Build → /sdlc-build (ux-designer [if has_ui] + fullstack-engineer × slices + qa-engineer)
Verify → /sdlc-verify (security-engineer + performance-engineer [if needs_performance_audit])
Ship → /sdlc-ship (devops-engineer)
Operate → /sdlc-operate (sre-engineer + data-engineer [if has_data_pipeline])

9 agents total (product-manager, ux-designer, fullstack-engineer, qa-engineer, security-engineer, performance-engineer, devops-engineer, sre-engineer, data-engineer)

Process

Parse feature request
Create ./projects/<feature-name>/ with docs/, handoffs/ subdirectories
Run Plan phase → product-manager interviews + produces scope.json + PRD
GATE: "Ready to start Build?" → on confirm: run /handoff → handoffs/plan-handoff.md → invoke /sdlc-build
Build phase completes → GATE: "Ready to start Verify?" → on confirm: run /handoff → handoffs/build-handoff.md → invoke /sdlc-verify
Verify phase completes → GATE: "Ready to Ship?" → on confirm: run /handoff → handoffs/verify-handoff.md → invoke /sdlc-ship
Ship phase completes → GATE: "Ready to Operate?" → on confirm: run /handoff → handoffs/ship-handoff.md → invoke /sdlc-operate
Compile final summary

Phase Transition Flow

/sdlc-plan
  └─ [GATE: "Ready to start Build?"]
       └─ /handoff → handoffs/plan-handoff.md
            └─ /sdlc-build
                 └─ [GATE: "Ready to start Verify?"]
                      └─ /handoff → handoffs/build-handoff.md
                           └─ /sdlc-verify
                                └─ [GATE: "Ready to Ship?"]
                                     └─ /handoff → handoffs/verify-handoff.md
                                          └─ /sdlc-ship
                                               └─ [GATE: "Ready to Operate?"]
                                                    └─ /handoff → handoffs/ship-handoff.md
                                                         └─ /sdlc-operate

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

1mo ago First seen · 115 lines · 42 tokens per session scan A 36810237931a

Subscribe to this mod's changes

sdlc is a command published in the GitHub repository saitarrun/Devforge-ai (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,320 once invoked, about $0.0002 per session on Opus 5.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-31.

Claude Code Planning Project management agentic-ai ai-agents automation claude-code-plugin codex-plugin

poam-review

Review and manage Plan of Action & Milestones (POA&M).

GRCEngClub/claude-grc-engineering · 14 tokens

g-forge

G-Forge workflow commands. Subcommands — help, status, resume, doctor, audit, init, kickoff, onboard, brief, roadmap, intake, plan, forecast, blast-radius, execute, review, doc-review, align, afk, specialize, update, skill-design, skill-validate, adr, docs, wiki, patterns, telemetry, identity, retro, listen, optimize…

onlygian/G-Forge · 93 tokens

sdlc