sdlc-kernel

Defines the shared protocol, phase graph, and conventions for the sdlc-* SDLC framework.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running an AI-assisted software development lifecycle need every phase skill and subagent to follow the same contract — the same gates, state files, path resolution rules, and verdict vocabulary — without duplicating thousands of lines of shared instructions that drift out of sync. ## Core Features & Use Cases - Shared protocol definition: Specifies the six-line preamble every sdlc-* skill uses, with project-first path resolution for framework assets under .agent/. - Phase graph and gates: Documents the ten phases (intake through done) and gate verdicts (pass, revise, block) that all sibling skills reference. - Binding rules and subagent contract: Enforces rules like no stack literals, hash artifacts at gate time, and never grant your own gate, plus the tool permissions of five subagents such as spec-writer and quality-guardian. - Use Case: When authoring a new sdlc-* phase skill or debugging why /sdlc --doctor reports a duplicated gate procedure, read this kernel to learn the exact contract instead of copying step files into the skill. ## Quick Start Read the sdlc-kernel skill to learn the shared protocol and rules before creating or modifying any sdlc-* phase skill.

Frequently Asked Questions about sdlc-kernel

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

FAQPage Schema
What is the sdlc-kernel skill used for?▼

The sdlc-kernel skill holds the shared contract for the sdlc-* SDLC framework: the protocol preamble, ten-phase graph, gate verdicts, and binding rules. It is read by other skills and subagents, never invoked directly by users.

How do sdlc-* skills share common instructions without duplication?▼

Each skill repeats only a six-line pointer preamble that references shared step files under .agent/steps/. Copying the full contents of gate.md or context-loader.md into a SKILL.md is treated as a bug that /sdlc --doctor reports.

Can a project override individual framework templates or rules?▼

Yes. Framework assets resolve project-first: a repository's own .agent/ copy wins over the plugin root copy. Only project-context.yaml and .agent/state/ are always project-local and never read from the plugin root.

What are the gate verdicts in the SDLC framework?▼

Gates return pass, revise, or block, matching the review report vocabulary where pass means ship. A skill must never grant its own gate; unevaluable checks are recorded as unknown, and only blocker and major findings trigger loop-backs.

Why does the spec-writer subagent have no Bash access?▼

Spec-writer is limited to Read, Grep, Glob, Write, and Edit so a spec author cannot run the test suite. Similarly, quality-guardian lacks Write and Edit so a reviewer cannot auto-apply changes it promised not to make.