sdlc

Plugin sdlc from marketplace carlpaton in carlpaton/skills. Commands read from the repo's manifest — yesterday.

Skills (6)

• deploy

  Step 5 of the SDLC. Check that verified work is ready to release (PRs reviewed and merged, checks green, pre-flight list done), write the release record and notes, and take it through the project's deployment procedure with an explicit human approval at every environment, production included. Use wh

• design

  Step 2 of the SDLC. Turn an accepted intent into a spec (spec/<issue#>-<slug>.md) containing requirements, acceptance criteria and a design that follows the project's conventions, via a PR, or sync an existing spec when its intent or the conventions have changed. Use when given an issue number or in

• issue

  Create a well-formed GitHub issue in the same format as the repo's issue forms, and optionally group it with labels, a project and a milestone, creating any that do not exist yet. Use when the user wants to raise, log or file an idea, request, feature, bug or task as a GitHub issue.

• maintain

  Step 6 of the SDLC. Take a signal from a released system (a monitoring alert, a scan finding, an incident, a user report), investigate it read-only, triage it as fix now, schedule or dismiss, and write the outcome back into the loop as an issue for /plan. Also writes post-mortems for incidents and p

• plan

  Step 1 of the SDLC. Turn a GitHub "Idea" issue into an intent file (intent/<issue#>-<slug>.md) via a PR, or sync an existing intent file when its issue has changed. Use when given an issue number to plan, or asked to check whether an issue and its intent file have drifted.

• setup

  Step 0 of the SDLC, run once per project. Bootstrap the foundations later steps rely on by recording how the code will be built (architecture, testing, conventions) as committed files, for a new or an existing code base. Use when starting a project, adopting the SDLC in a repo, or when those foundat

Similar plugins