sdlc-chain

Validates that projects commit the six-stage SDLC artifact chain to git.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects built by fast-moving AI agents often skip planning, specification, and verification, leaving no audit trail. This Skill enforces the AI-native SDLC by checking that every project commits six artifacts — intent, spec, plan, verification, launch checklist, and incident log — to git, so each stage of work is documented and reviewable. ## Core Features & Use Cases - Six-stage chain check: Verifies the presence of intent.md, spec.md, plan.md, VERIFICATION.md, LAUNCH-CHECKLIST.md, and INCIDENTS.md, accepting legacy filenames like Requirements.md or Proposed Plan.md as aliases. - Git commit verification: Confirms each artifact is tracked by git, since an uncommitted local file is not an audit trail. - Grandfathering ratchet: A baseline file exempts pre-existing projects from blocking while requiring all new projects to comply; healed projects are removed from the list permanently. - Use Case: Before pushing a new project, run the checker to confirm the intent, spec, and plan exist and are committed; the gate exits 1 and names the missing stage if the chain is broken. ## Quick Start Run the sdlc-chain checker on my project to verify its intent, spec, plan, verification, launch, and incident artifacts are all committed to git.

Frequently Asked Questions about sdlc-chain

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

FAQPage Schema
How do I check if a project has proper SDLC documentation?

Run node check.mjs with the project directory path to verify all six stages — intent, spec, plan, verification, launch checklist, and incidents — exist and are committed to git. Use --all to check every project or --enforce to fail on missing artifacts.

What artifacts does the AI-native SDLC require per project?

The playbook defines six stages: intent.md (plan), spec.md (design), plan.md (build), VERIFICATION.md (test), LAUNCH-CHECKLIST.md (deploy), and INCIDENTS.md (maintain). Each must be committed to git so the chain doubles as an audit trail.

Does the checker accept existing filenames like Requirements.md?

Yes, each stage accepts legacy aliases such as Requirements.md, Proposed Plan.md, Raw Idea.md, STATUS.md, and watchdog.json. Aliases satisfy the chain but are reported as aliases, while canonical names are recommended for new work.

Why does the check fail when artifact files exist locally?

The checker verifies each artifact is tracked by git using git ls-files, because an uncommitted local file is not an audit trail. Commit the missing files to make the chain intact.

How does grandfathering work for legacy projects?

Projects listed in chain-baseline.json are reported but not blocked, while any project not on the list must have an intact chain. When a grandfathered project's chain becomes intact, it is removed from the list permanently, so the list only shrinks.