agentmods.dev

sdlc

sdlc is a command for Claude Code from HoangNguyen0403/agent-skills-standard. It costs 0 tokens per session (1,576 once invoked), scanned A, original, MIT.

A workflow router that examines the current request, project documents, and repository state, then selects the next step in a software development life cycle. An SDLC is the sequence from requirements and design through implementation and verification.

In plain words
What is it for?
Use it to continue work from an existing brief, plan, design, ticket, or implementation state.
Why use it?
It removes the need to decide manually which workflow or document should come next. It also keeps the handoff between business, product, and engineering work traceable.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 565repo +4 changed 5d ago A scan 0 tokens original MIT

Good fit Use it to continue work from an existing brief, plan, design, ticket, or implementation state.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hoangnguyen0403/agent-skills-standard/sdlc
View source ↗ HoangNguyen0403/agent-skills-standard npmjs.com
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.

Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/sdlc/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/sdlc)
Your own site
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/sdlc"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/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.

agentmods 80×15 button for sdlc

Your own site · 80×15
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/sdlc"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/sdlc.svg" alt="Reviewed on agentmods" width="80" 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,576 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01576
Opus 5 $0.00000 $0.00788
Sonnet 5 $0.00000 $0.00315
Haiku 4.5 $0.00000 $0.00158

Measured 5d ago against content hash ebce745f04a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

.claude/commands/sdlc.md · 105 lines

How it starts

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

Sdlc

Route a task to the next synced SDLC workflow based on current artifacts and repo state.

Input: $ARGUMENTS

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

Execute the following steps for $ARGUMENTS.

SDLC Router Workflow

Goal: Select the next native workflow without loading every workflow body, while preserving a traceable BA -> PM -> IT Department handoff for offshore delivery.

Steps

  1. Inspect state:

    • User request; infer operator_profile (business | hybrid | technical) per common-operator-profile and carry it in every Handoff Payload.
    • Search docs/brd/, docs/prd/, and docs/srs/ for a matching [slug]; if absent, use the newest BRD or git status. Slug = lowercase kebab-case, minted once at brainstorm-feature, reused verbatim downstream; never re-derived.
    • If multiple candidates exist, list them and ask whether to focus, consolidate, or sequence.
    • Baseline reference: docs/requirements-standards-baseline.md
    • Existing ticket, BRD-lite brief, PRD, SRS/FRS design, implementation plan, task list, walkthrough, UAT signoff, deployment report, release notes, and retro
    • Jira, ADO, Zephyr, or other MCP context when already configured
    • Changed files and current test status
    • Offshore delivery context: business owner, product owner, implementation owners, QA owner, timezone/cadence constraints, environments, release window, and dependency teams
    • Requirement trace health: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence

  2. Choose next workflow (apply tie-break order when multiple bullets match: (1) workflow explicitly named by the operator or by the latest recommended_next_workflow, (2) production-incident/urgent-regression signals, (3) earliest missing artifact along the chain below — never skip forward past a gap, (4) cross-cutting audits only on request or as a pre-release gate):

    • Unclear idea, missing business case, missing stakeholder owner, or missing measurable value (BRD-lite / Why, BA-owned intake) -> brainstorm-feature
    • BRD-lite exists or business direction is clear but product scope, priorities, acceptance criteria, rollout, or delivery plan are unclear (PRD / What, PM-owned planning) -> plan-feature
    • Scale, topology, capacity, or store choice unsettled, or an existing system needs an architecture audit -> system-design-session
    • PRD exists but technical behavior/contracts unclear (SRS/FRS / How) -> design-solution
    • Architecture, auth, trust boundaries, compliance controls, or agent/runtime safety need deeper technical validation -> design-solution
    • BRD-lite, PRD, or SRS/FRS exists but readiness unclear -> implementation-readiness
    • Approved plan with BRD/PRD/SRS trace and testable ACs needs code -> implement-feature
    • Production incident or urgent regression -> incident-hotfix
    • Bug ticket needs fix (non-urgent) -> dev-fix
    • Ticket or cross-functional change needs specialist fanout, AC coverage, and PR metadata review -> review-ticket
    • Design arrives as an artifact (diagram, doc, board export, IaC) and needs review -> review-system-design
    • PR diff needs focused merge-risk review -> code-review
    • Implementation GREEN but ACs lack executable E2E/mobile coverage, or an E2E suite is red after a previously green slice -> test-loop.
    • Code complete but unproven -> verify-work
    • Fix implemented and ticket has a UAT/Jira flow -> verify-bug
    • verify-work PASS on a feature, business acceptance not yet granted -> uat-signoff
    • Business acceptance granted and release window open -> deploy-release
    • Deployed and needs user-facing communication -> publish-notes
    • Trace health unknown before release or handoff -> traceability-audit
    • Session ending with unfinished work or context handoff -> session-report
    • Deployed or communicated, capture standards/process lessons -> retro-learn
    • Repo-wide health/debt question with no single feature in scope -> codebase-review

Read the full file on GitHub · 105 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 Changed · +1 lines ebce745f04a3
  2. 9d ago First seen · 104 lines · 0 tokens per session scan A c69f57c8e28f

Subscribe to this mod's changes

sdlc is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,576 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-09-03.

PlanningProject managementReactbest-practicescoding-standardsflutternestjsnextjs
Related

Other commands, from other repositories

plan

PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.

first-fluke/fullstack-starter · 35 tokens

schedule

Register a scheduled agent job from a natural-language schedule request — parse the interval, resolve agent-id + prompt + workspace, call oma schedule:add, then confirm with oma schedule:list.

first-fluke/fullstack-starter · 35 tokens

coordinate-pro

Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.

first-fluke/fullstack-starter · 19 tokens

coordinate

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens

exec-plan

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.

first-fluke/fullstack-starter · 20 tokens

work

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens