Twelve SDLC Agent Skills that carry a project from idea to a deployed, verified system — requirements, architecture, UX foundations, implementation plan, repo scaffolding and deployment, then a per-feature loop of detailed design, UI design, implementation and independent acceptance verification.
A shared ID vocabulary and an append-only traceability matrix keep the twelve behaving as one pipeline.
Skills 12 in the Claude listing
Acceptance verification The independent auditor that closes the per-feature loop. Detailed design Produces the per-feature technical design — the first skill in the construction loop, run once for each vertical slice as it reaches the front of the implementation plan. Feature implementation Executes a feature's tasks.md against its designs, producing working, tested, committed code — the construction step of the per-feature loop. Implementation planning Turns finalized requirements and design documents into an executable, sequenced build plan. Initial deployment Takes the project from deploy-ready to running in the cloud — the last mile scaffolding stopped short of. Pipeline verify The cross-document seam checker for the SDLC pipeline. Project scaffolding Turns the pipeline's design documents into a running system. Requirements engineering Runs the requirements-engineering phase — the first SDLC step, upstream of design. Sdlc orchestrator Drives the pipeline's per-feature construction loop and routes lifecycle events — deliberately thin: zero design or build logic; it computes position, invokes the right stage skill, and routes outcome Software architecture Designs the software architecture for a new application, service, or major feature through a structured interview, then produces an architecture document (arc42-style, with C4 diagrams in Mermaid and Ui design Designs the screens — the presentation half of each feature's low-level design, sibling to detailed-design. Ux foundations Establishes the UX and design foundations for an application before feature work begins — the "architecture of the UI." Consumes the upstream SRS (docs/srs.md) and architecture document (docs/architec