amdluigi-sdlc

Plugin amdluigi-sdlc from marketplace amdluigi in amdluigi/sdlc. Commands read from the repo's manifest — today.

Skills (24)

• sdlc-accessibility-browser

  Use when a change creates or modifies rendered web or mobile UI, user interaction behavior, responsive layout, navigation or focus behavior, accessibility semantics, or browser-only runtime behavior.

• sdlc-api-compatibility

  Use when a change adds, removes, or modifies a consumer-visible request, response, command, event, schema, serialization, error, SDK, generated-client, or versioning contract, including behavior observable by an independently deployed or external consumer.

• sdlc-change-contract

  Use when always when enabled to establish the change contract.

• sdlc-continuous-improvement

  Use when a task produces a correction, repeated merge step, recurring review finding or coverage gap, explicit learning request, or an SDLC core upgrade changes core responsibilities.

• sdlc-data-migration

  Use when a change transforms, backfills, moves, reinterprets, or deletes durable production data; changes a production schema in a way that requires old and new application or schema versions to coexist; or introduces a migration whose failure could leave persistent state partial or invalid.

• sdlc-debugging

  Use when a bug or unexplained failure is in scope.

• sdlc-dependency-supply-chain

  Use when a change adds, removes, replaces, updates, pins, vendors, generates, downloads, or changes the resolution or execution of a third-party dependency, package manager, registry, lockfile, build plugin, action, container base, or fetched build artifact.

• sdlc-evaluator

  Use only when a maintainer explicitly asks to audit or review completed sdlc-orchestrated work after the fact (friction, recurring corrections, or whether a targeted instruction change to sdlc or a delegated skill is warranted). Never load as a side effect of any other skill trigger, and never load

• sdlc-implementation

  Use when code or configuration changes are required.

• sdlc-incident-response

  Use when an active production incident, material service degradation, security event, or customer-impacting data integrity failure requires containment, recovery, or a post-incident follow-up.

• sdlc-observability

  Use when a change adds, removes, or modifies logs, metrics, traces, dashboards, or alerts; introduces or changes a service, queue, scheduled-job, or other asynchronous production boundary; or has an accepted requirement for new diagnostic or operational signals.

• sdlc-operational-readiness

  Use when production data, public contracts, runtime or deployment configuration, infrastructure, background processing, or rollout are affected.

• sdlc-performance-concurrency

  Use when a change has an explicit latency, throughput, capacity, or resource objective; modifies an evidenced hot path; or introduces or changes concurrency, parallel work, batching, caching, streaming, queueing, rate control, or shared mutable state.

• sdlc-planning

  Use when the change is Standard or Significant.

• sdlc-pr-handoff

  Use when always before completion when enabled to prepare PR handoff.

• sdlc-prd

  Use when a new project, a new user-facing or product-facing feature, or a Significant internal feature introduces a new capability.

• sdlc-project-memory

  Use when always when enabled.

• sdlc-project-standards

  Use when always when enabled.

• sdlc-release-launch

  Use when a completed change is being published, deployed, released, launched, rolled out, tagged, or otherwise made available to an external audience.

• sdlc-review

  Use when always before completion when enabled.

• sdlc-security-auth

  Use when external input, stored or sensitive data, network access, identity, permissions, secrets, dependencies, or user-visible output are affected.

• sdlc-tdd

  Use when new behavior or a bug fix changes executable behavior.

• sdlc-testing

  Use when behavior, bug, refactor, tests, or non-trivial verification are in scope.

• sdlc

  Use when creating, modifying, debugging, fixing, or reviewing code, including work likely to become a pull request, before implementation begins. Also use when scope is unclear, a request bundles outcomes, verification or review might be skipped, delegated coding needs guardrails, project context mu

Slash commands (3)

• /amdluigi-sdlc:sdlc-check

  Report which SDLC delivery phases have an implementation and which are missing. Use at the start of SDLC work, before relying on a lifecycle phase, or whenever a capability appears unavailable.

• /amdluigi-sdlc:sdlc-download

  Install the bundled SDLC implementations this project is missing. Use after a check reports a gap and the developer agrees to install, or when asked to repair or complete an SDLC installation.

• /amdluigi-sdlc:sdlc-init

  Create the SDLC project configuration when the project has none. Use before the first non-trivial change in a project with no .sdlc/config.json, or when a developer asks to configure, enable, disable, or replace lifecycle phases.

Similar plugins