sdlc-code

Implements use cases from technical designs following layered architecture and trace tagging rules.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/juartaurus98/codebase --skill sdlc-code-juartaurus98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-code
Source: https://github.com/juartaurus98/codebase/tree/main/.claude/skills/sdlc-code
Command: npx skills add https://github.com/juartaurus98/codebase --skill sdlc-code-juartaurus98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved technical design into working source code without silent design drift, enforcing layer order, traceability tags, and quality gates so every implemented scenario stays reviewable and auditable. ## Core Features & Use Cases - Design-driven implementation: Reads the technical design document and component map, then creates or modifies exactly the files the design specifies, stopping when the design is under-specified or conflicts with the codebase. - Layered, traceable code generation: Builds in the stack profile's layer order and tags entry points with @trace.implements annotations linking code back to use case scenarios. - AI prompt registry handling: Creates new versioned prompt YAML files for AI features without editing published versions, wiring call sites through a mockable LLM protocol. - Use Case: A tech lead approves a design for a three-use-case feature; the skill fans out one code-implementer agent per use case, runs lint/typecheck/build checks, and records the G4 gate verdict. ## Quick Start Invoke /gen-code with a feature or use case ID, for example: implement FEAT-042 from its technical design document.

Frequently Asked Questions about sdlc-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a feature from a technical design document?▼

Invoke /gen-code with the feature or use case ID. The skill reads the design's component map, lists the files to create or modify at a checkpoint, then implements in the stack profile's layer order with trace tags on entry points.

What happens if the technical design is incomplete or not ready?▼

The input check returns NO_SOURCE or NOT_READY and the skill stops with a report instead of guessing. Implementing from an under-specified design would hide unreviewed design decisions in the code.

Does this skill write unit tests along with the implementation?▼

No. Tests are deliberately owned by separate /gen-testcase and /unittest commands in a different context window, so tests are not shaped to the implementation's bugs.

How are AI prompt versions handled during implementation?▼

A new versioned YAML file is added to the prompt registry; published versions are never edited in place. The call site is wired through an LLM protocol so it can be mocked in unit tests.

What happens when lint or typecheck keeps failing after implementation?▼

The skill retries fixes at most three rounds, then stops and reports, since repeated failure usually indicates a design problem. It never disables rules or loosens types to force a green result.