MCKRUZ/claude-code-sdlc

MCKRUZ/claude-code-sdlc

Command

Audit the content of your pre-Build artifacts: which ones have gone stale relative to the things they depend on, what a change would put at risk, and the full change trail of any one artifact.

MCKRUZ/claude-code-sdlc

Command

Analyze gate results across completed phases in the current project's state.yaml to identify which gates are useful and which are candidates for adjustment.

MCKRUZ/claude-code-sdlc

Command

Run cross-document analysis on the intake corpus and draft the one-page workshop brief, with the human curating what makes the page. Works inside an SDLC project or standalone against any folder of documents.

MCKRUZ/claude-code-sdlc

Command

Bind one spec to its delivery channel and overlay that channel's acceptance dimensions onto the spec's existing ## Acceptance Checks. This is the bind beat after /sdlc-feature (decompose) and /sdlc-experience (author): decompose → author → bind. It reads the channel descriptor and the Phase-2 interaction spec, injects…

MCKRUZ/claude-code-sdlc

Command

Start or continue a coaching conversation for the current SDLC phase. Coaching mode uses adaptive dialogue instead of rigid step lists to guide the user through phase requirements.

MCKRUZ/claude-code-sdlc

Command

Give Data a first-class drafting seat: the data contract (PII-classified), the data-readiness assessment, and the lineage / audit design for a feature or spec. It sharpens Scope, surfaces the PII that drives risk tier, and turns readiness gaps into tracked decisions. Interview-driven like /sdlc-coach: the data-analyst…

MCKRUZ/claude-code-sdlc

Command

Verify that the installed harness will actually run in this repo, and tell the developer exactly what to do about anything that won't.

MCKRUZ/claude-code-sdlc

Command

Generate stakeholder-friendly narrative companions for SDLC artifacts.

MCKRUZ/claude-code-sdlc

Command

Author the golden set — the acceptance criteria for probabilistic behavior — for a spec on an llmpowered channel. Bizreq owns the scenarios, Data owns the data; the two are authored collaboratively. This command is a thin wrapper around the existing eval-builder harness skill: it adds no new script, authors no CI…

MCKRUZ/claude-code-sdlc

Command

Author the craft of a surface — the user journey, the surface layout, and the channel interaction spec — for one channel-bound spec. This is the author beat between /sdlc-feature (which decomposes) and /sdlc-channel (which binds): decompose → author → bind. It routes by the feature's channel to the right designer …

MCKRUZ/claude-code-sdlc

Command

Drive the epic → feature → spec decomposition that the plugin lacks today — the "featuring" hop where you decide how a feature is delivered (which customer channels, which personas) and carve it into buildable specs. Output is feature-brief.md, authored on every channel-bound feature. This is interview-driven like…

MCKRUZ/claude-code-sdlc

Command

Run the 7-gate validation system for the current (or specified) SDLC phase without advancing.

MCKRUZ/claude-code-sdlc

Command

Install (or refresh) the standard-aligned delivery harness in the current repo, independent of a full /sdlc-setup. Use this to add the harness to a repo that already has .sdlc/, or to pull the latest harness after a plugin update (the harvest loop).

MCKRUZ/claude-code-sdlc

Command

Process external reference documents (RFPs, API specs, vendor docs, decks) into a cataloged, token-budgeted set of summaries for use across the engagement. This is the Phase 0 Step 0c workflow wrapped as one command, so no one runs the cataloger script by hand.

MCKRUZ/claude-code-sdlc

Command

Run exit gate checks for the current phase and advance to the next phase if all gates pass.

MCKRUZ/claude-code-sdlc

Command

Render all artifacts for the current (or specified) phase into a self-contained HTML report for stakeholder review.

MCKRUZ/claude-code-sdlc

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…

MCKRUZ/claude-code-sdlc

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.

MCKRUZ/claude-code-sdlc

Command

Run a structured review of the current phase's artifacts from multiple perspectives.

MCKRUZ/claude-code-sdlc

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.

MCKRUZ/claude-code-sdlc

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.…

MCKRUZ/claude-code-sdlc

Command

Initialize SDLC lifecycle management for a project.

MCKRUZ/claude-code-sdlc

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.

MCKRUZ/claude-code-sdlc

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.