sdlc

The software delivery lifecycle: an audit for repositories built without one, tickets, change review for agent-written code, a local CI run before each push, test strategy, and release with rollback.

• Version 0.2.0
• 8 skills
• 1 gate check
• Running on this site: Board

What it does

The lifecycle a change moves through, from request to production and back: request, RFC, decision, build, review, test, gate, release, observe, incident. This module writes the lifecycle down, connects each stage to the module that serves it, and fills the stages no other module covers: tickets, code review, testing and release. Its audit is the entry point for a team new to the suit, and it runs on a repository with no other module installed.

Coding agents write code fast. A product built that way breaks in the stages around the code: no ticket says what done means, no test runs before merge, nothing stops a bad deploy, nobody can roll back. /sdlc:sdlc-audit lists those gaps in the order they cost the most.

Install

Add the marketplace at release v0.1.0 once, then install the plugin and restart Claude Code.

claude plugin marketplace add uncovertechtalent/cto-powersuit#v0.1.0
claude plugin install sdlc@cto-powersuit

Skills

• /sdlc:change-review

  Review a change before a person approves it, with a checklist for agent-written code: diff size, scope against the ticket, tests touched, secrets, new dependencies, migrations, generated files and changed tests.

• /sdlc:pre-push

  Run the check jobs of the repository's own GitHub Actions workflows locally, in a microVM with preloop, before a push, so a failing check is fixed before anything leaves the machine.

• /sdlc:release

  Prepare a release: a changelog entry drafted from the main line, a rollback plan, the feature flags the release depends on, and the release record with tag, changelog and deploy run.

• /sdlc:sdlc-audit

  Audit a repository for the stages of a software delivery lifecycle and return the missing ones ranked by the damage each does for what the repository ships to, each with the module or skill that fills it.

• /sdlc:sdlc-init

  Map the repository's delivery lifecycle and write docs/sdlc.md: a stage table with entry and exit criteria, an owner per stage, the record each stage leaves and the installed module that serves it, with the uncovered stages listed as gaps.

• /sdlc:test-strategy

  Decide what gets tested at which level (unit, integration, end to end, smoke) and define the one command an agent or a person runs before opening a pull request.

• /sdlc:ticket

  Write a ticket from a request, a bug report, a chat or a postmortem action item: problem, testable acceptance criteria, risk, and labels for type, area, priority and status.

• /sdlc:work-item

  Walk one change through the lifecycle stages and link the record at each stop: ticket, RFC or ADR, branch, pull request, test run, gate run, deploy record and dashboard.

Gate checks

The checks this plugin adds to the deploy gate of the gate module, each with a pass fixture and a fail fixture:

• sdlc.traceability

Source

The CTO powersuit is a set of agent skills, one module per CTO function from the deploy gate to the hand-over, that one person uses to run a company's whole engineering platform. sdlc is one of its 18 plugins, published by Stefan Coetzee.

The skills, templates, checks, fixtures, and the full README of sdlc at release v0.1.0: github.com/uncovertechtalent/cto-powersuit/tree/v0.1.0/plugins/sdlc. License: MIT. Every plugin of the powersuit: CTO powersuit.