sdlc-kit-extended

Skills

13 in the Claude listing

• Sdlc apiUse when the user asks to document an API, design a REST endpoint, create an async event contract, define a gRPC service, specify a webhook, or when they invoke `/sdlc-kit:api`.
• Sdlc c4Use when the user asks to document or update the system architecture using the C4 model (levels 1–3), draw a context/container/component diagram, or invokes `/sdlc-kit:c4`.
• Sdlc design systemUse when the user wants to create, list, or change the status of a design-system entry — a design token (atomic value), a component (reusable UI spec) or a pattern (recurring combination of components
• Sdlc design validationUse as Gate 3 of the frontend UX workflow — validates that UX research (Gate 1) and Design System initialization (Gate 2) are complete and consistent before a TRD is authored (Gate 4).
• Sdlc domainUse when the user asks to model the domain, define a bounded context, add an aggregate/domain event/context contract, or curate the ubiquitous language — or when they invoke `/sdlc-kit:domain`.
• Sdlc epicUse when the user wants to create, list, or change the status of an epic — a large deliverable decomposed from a PRD that groups related stories (each often becoming a spec trio under `04-specs/`).
• Sdlc impactUse when the user wants a change-impact analysis over the vault's wikilink graph.
• Sdlc incidentUse when the user wants to record, walk, or close a production incident — the real-time event report plus the post-mortem lessons doc.
• Sdlc milestoneUse when the user wants to create, list, or change the status of a milestone — a delivery window that groups one or more epics toward a single target date, with RAG-style health (planned / on-track /
• Sdlc steerUse when the user wants to define or update the project's steering documents — product vision, technical principles, or team standards.
• Sdlc traceUse when the user wants a requirement-to-artifact traceability matrix across the SDLC vault — "trace coverage", "traceability", "requirement coverage", "which PRDs have no implementation", "which desi
• Sdlc trdUse when the user wants to record, review, or transition a Technical Requirements Document (TRD) — the cross-cutting non-functional baseline (performance, scalability, reliability, security, privacy/L
• Sdlc uxUse when the user wants to run Gate 1 of the frontend UX workflow — UX Research + Product Design — for a new initiative or feature with a user-facing surface.