Convert user intent into a spec-first SDLC pipeline with phase gates.
npx skills add https://github.com/esxr/sdlc-skill --skill spec-first-sdlc
Please help me install this Agent Skill. Skill: spec-first-sdlc Source: https://github.com/esxr/sdlc-skill/tree/main/. Command: npx skills add https://github.com/esxr/sdlc-skill --skill spec-first-sdlc
Spec-First SDLC provides a structured approach to transform human intent into traceable software artifacts. It reduces ambiguity, ensures design-before-code discipline, and provides a clear path from requirements to implemented software with review gates at each phase.
Prepare your Intent & Constraints document and optional design artifacts, then run this Skill. Claude will generate the High-Level Design, ADR-Lite, revised HLD, Executable Implementation Specification, and from that, code in src/ and tests in tests/. Review each phase before proceeding.
High-intent search queries and answers about installing and using this skill.
Spec-first SDLC transforms requirements into structured design artifacts—High-Level Design, ADR-Lite decisions, and Executable Implementation Specification—with human review gates at each phase, ensuring traceability from intent through implementation.
ADR-Lite captures architecture decisions with context, rationale, and consequences in a lightweight format. It creates a traceable record linking design choices to requirements and code, reducing ambiguity and enabling future maintainers to understand the 'why' behind decisions.
Yes. The Spec-First SDLC pipeline generates executable code and tests directly from the validated Executable Implementation Specification, automating the translation from design intent to working implementation with built-in test coverage.
Implement phase gates with mandatory human approval at Intent, HLD, ADR, and EIS stages. This enforces review discipline, prevents premature coding, and ensures requirements, architecture decisions, and implementation stay aligned throughout the project lifecycle.
Spec-first development prioritizes design artifacts and requirements clarification before writing code, reducing rework and ensuring traceability. Code-first typically begins implementation immediately, risking design misalignment and incomplete documentation of architectural decisions.
No. Start with an Intent & Constraints document describing your requirements and goals. The pipeline generates HLD, ADRs, and implementation specs from that starting point, though you can also provide optional existing design artifacts to build upon.
dfrysingerCapture user intent and constraints into a draft goals.md for a QRSPI pipeline.
cslsoftwaresStandardize SDLC documentation artifacts across planning, development, testing, and operations.
wth461694678Orchestrate a 9-phase development pipeline from requirement to testing.
ChoiHyunjinExecute agile development cycles for trading applications with risk validation.
