sdlc plugin
Software delivery lifecycle: an audit for repositories built without one, the lifecycle map, tickets, review, test strategy and release, with a traceability gate check.
How to install the sdlc plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add uncovertechtalent/cto-powersuit
/plugin install sdlc@cto-powersuitWhat's inside sdlc
8 parts read from the plugin's own files.
Skills 8
Claude loads it when the task matches- 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. Use when a pull request is open, before asking a person to review, or when an agent wrote most of the diff. Reads the repository's recorded decisions and conventions first, so a deliberate choice is not flagged; with `kb` it also reads a private knowledge base on the user's machine and posts one comment that cites public files only. Activates on "/change-review", "review this PR", "check this diff", "review the agent's change", "is this ready to merge".
- 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. Use before `git push`, before opening a pull request, after an agent changed files a workflow checks, or to reproduce a failed CI run. Activates on "/pre-push", "run CI locally", "test before I push", "preloop", "reproduce the CI failure".
- 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. Use before a deploy that users will notice, before tagging a version, or when nobody knows how to undo the last release. Activates on "/release", "prepare the release", "write the changelog", "how do we roll back", "tag a version".
- 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. Use when a team new to the suit wants to know where to start, typically on a repository built fast with coding agents and no process around them. Runs with no other module installed. Read only. Activates on "/sdlc-audit", "audit our lifecycle", "what is missing in this repo", "why does our vibe-coded app keep breaking", "where do we start".
- 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. Use when a team adopts the suit, or when nobody can say how a change gets from request to production. Activates on "/sdlc-init", "map our lifecycle", "write the sdlc doc", "how do changes ship here", "set up the 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. Writes the test section of docs/sdlc.md. Use when a repository has no tests, tests that CI never runs, or tests nobody trusts. Activates on "/test-strategy", "what should we test", "set up the pre-PR check", "our tests are flaky", "add tests to this repo".
- 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. Also sets up the label scheme in the tracker. Use when work is about to start without a ticket, or when a request is too vague to build. Activates on "/ticket", "write a ticket", "open an issue for", "turn this into a ticket", "set up our labels".
- 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. Use when starting a change, when handing a change to another person or agent, or when asked where a change stands. Activates on "/work-item", "walk this change through", "where is this change", "trace this ticket", "start work on".
Using sdlc in Claude Code
Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update sdlc@cto-powersuit
- Refresh the marketplace
- /plugin marketplace update cto-powersuit
- Turn it off for now
- /plugin disable sdlc@cto-powersuit
- Remove it
- /plugin uninstall sdlc@cto-powersuit
Skills in sdlc
- change-reviewuncovertechtalent/cto-powersuit
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. Use when a pull request is open, before asking a person to review, or when an agent wrote most of the diff. Reads the repository's recorded decisions and conventions first, so a deliberate choice is not flagged; with `kb` it also reads a private knowledge base on the user's machine and posts one comment that cites public files only. Activates on "/change-review", "review this PR", "check this diff", "review the agent's change", "is this ready to merge".
2 files8stars - sdlc-audituncovertechtalent/cto-powersuit
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. Use when a team new to the suit wants to know where to start, typically on a repository built fast with coding agents and no process around them. Runs with no other module installed. Read only. Activates on "/sdlc-audit", "audit our lifecycle", "what is missing in this repo", "why does our vibe-coded app keep breaking", "where do we start".
22 files8stars - pre-pushuncovertechtalent/cto-powersuit
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. Use before `git push`, before opening a pull request, after an agent changed files a workflow checks, or to reproduce a failed CI run. Activates on "/pre-push", "run CI locally", "test before I push", "preloop", "reproduce the CI failure".
8stars - releaseuncovertechtalent/cto-powersuit
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. Use before a deploy that users will notice, before tagging a version, or when nobody knows how to undo the last release. Activates on "/release", "prepare the release", "write the changelog", "how do we roll back", "tag a version".
8stars - sdlc-inituncovertechtalent/cto-powersuit
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. Use when a team adopts the suit, or when nobody can say how a change gets from request to production. Activates on "/sdlc-init", "map our lifecycle", "write the sdlc doc", "how do changes ship here", "set up the sdlc".
8stars - test-strategyuncovertechtalent/cto-powersuit
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. Writes the test section of docs/sdlc.md. Use when a repository has no tests, tests that CI never runs, or tests nobody trusts. Activates on "/test-strategy", "what should we test", "set up the pre-PR check", "our tests are flaky", "add tests to this repo".
8stars - ticketuncovertechtalent/cto-powersuit
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. Also sets up the label scheme in the tracker. Use when work is about to start without a ticket, or when a request is too vague to build. Activates on "/ticket", "write a ticket", "open an issue for", "turn this into a ticket", "set up our labels".
8stars - work-itemuncovertechtalent/cto-powersuit
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. Use when starting a change, when handing a change to another person or agent, or when asked where a change stands. Activates on "/work-item", "walk this change through", "where is this change", "trace this ticket", "start work on".
8stars
sdlc plugin questions
How do I install the sdlc plugin?
In Claude Code run /plugin marketplace add uncovertechtalent/cto-powersuit, then /plugin install sdlc@cto-powersuit.
What does the sdlc plugin include?
sdlc bundles 8 skills.
How do I update or remove the sdlc plugin?
Update it with claude plugin update sdlc@cto-powersuit in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall sdlc@cto-powersuit.
What license is the sdlc plugin under?
MIT, as stated in the plugin's manifest.