sdlc-next
73Command
Run exit gate checks for the current phase and advance to the next phase if all gates pass.
Command
Run exit gate checks for the current phase and advance to the next phase if all gates pass.
Command
Render all artifacts for the current (or specified) phase into a self-contained HTML report for stakeholder review.
Command
Traceability normally flows forward (requirement → spec → code). This command runs it backward: when a spec merges, it surfaces the pre-Build artifacts that spec implies an edit to — requirements.md, epics.md, feature-brief.md, business-rules.md — so they stop silently drifting from what actually shipped. It reads as…
Command
Read across the three advisory ledgers at once and surface what keeps happening — the retro question the per-round commands can't answer on their own. It reports four patterns.
Command
Run a structured review of the current phase's artifacts from multiple perspectives.
Command
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.
Command
Give Bizreq a first-class drafting seat: the business rules (a BR-NN decision table) and the golden scenarios (SCEN-NN) that pin down what "correct" means before anyone builds. Each BR-NN becomes an Acceptance Check on the spec (advisory / soft traceability); each SCEN-NN seeds the golden set at /sdlc-evals.…
Command
Initialize SDLC lifecycle management for a project.
Command
Turn a story into a ready spec (specs/NNNN-name.md) that clears the Definition of Ready before anyone builds it. This is the Intent beat of the Build loop wrapped as one command: scaffold → author → enforce the DoR → confirm the risk tier with a human. No spec, no build.
Command
Open a spike (spikes/NNNN-name.md) for a question the pod cannot yet answer. This is the escape hatch for the one situation /sdlc-spec cannot serve: a story that fails the Definition of Ready not because it is badly written, but because nobody knows the answer.
Command
Display the current SDLC progress for this project.
Command
Upgrade a repo's installed delivery harness to the plugin's current version using the install receipt (.claude/harness-manifest.json). Unlike installharness.py --force, this never clobbers a repo's adaptations: files still factory-original are brought forward, adapted files are left alone, and files changed on both…
Command
See what a pre-Build artifact used to say, diff any two of its versions, and — when a change went wrong — roll it back. This is the content complement to /sdlc-audit-artifacts: that command tracks that an artifact changed (the metadata trail); this one recovers what it said at each version and restores it if needed.
Command
Show guidance for the current SDLC phase including what to do, which skills to use, and what artifacts to produce.
Agent
System-design and architectural decisions: new services, cross-cutting changes, scaling and data-model calls, public API contracts. Use for HIGH-risk design work BEFORE a spec is built against it. Produces a design with trade-offs and a recommendation — it does not write code.
Agent
Fixes build, compile, type, and lint errors with minimal diffs. Use PROACTIVELY (auto-spawn) the moment a build or lint step fails. Gets the build green fast — no architectural changes, no scope expansion. Pairs with the Stop hook, which won't let a turn end on a broken build.
Agent
Root-causes a failing test, exception, or wrong behavior via hypothesis elimination, in an isolated context. Use when the cause isn't obvious. Returns a distilled diagnosis + a minimal reproduction — it does not apply the fix (that happens under the bug-fix procedure).
Agent
Grades a change against its spec, check by check, and posts an advisory verdict. Use before a PR is approved, or invoke locally before pushing. The grader NEVER grades its own work — it runs in a fresh context and did not write the code.
Agent
Produces an implementation plan for a spec before code is written. Use for any MEDIUM or HIGH spec, or any feature touching 5+ files / a new service. Returns a sequenced plan with files to touch, order of changes, risks, and unknowns — it does NOT write code.
Agent
Reviews changes on gated paths or HIGH-risk specs for security defects. Use PROACTIVELY when a change touches auth, identity, payments, PII, migrations, infra, the pipeline, or prompt/model/tool definitions. BLOCKS on a HIGH-severity finding; advises otherwise.
Agent
Reviews user-facing Angular changes for UX quality: every state exists (loading, empty, error, success), accessibility basics hold, components follow the codebase's existing patterns, and the flow works end-to-end. Angular-aware — also catches the framework's own failure modes. Use PROACTIVELY when a change adds or…
Skill Claude CodeCodex
Add a new endpoint / MediatR command or query / handler / service the way this .NET codebase already does it. Use when building an API surface, a CQRS handler, a controller, a validator, or a DI registration in a .NET / Clean Architecture repo. Finds the one canonical example and mirrors its layering, validation…
Skill Claude CodeCodex
Add a new endpoint / route / use case / service the way this Node + TypeScript codebase already does it. Use when building an API surface, a request handler, a validator, a port/adapter, or a container registration in a Node/TypeScript repo. Finds the one canonical example and mirrors its layering, validation, error…
Skill Claude CodeCodex
Add a new module / CLI command / service function / loader the way this Python codebase already does it. Use when building a public surface, a command entry point, a data loader, a validator, or a new package module in a Python / uv repo. Finds the one canonical example and mirrors its layering, typing, error model…