ai-native-sdlc

Solid

Drive a change through an AI-native software development lifecycle as a loop of committed, machine-readable artifacts — intent.md, spec.md, plan.md, diff plus tests, PR review, control bands — and make the stage order enforceable with a PreToolUse hook and a CI gate instead of relying on discipline. Use when the user wants to start a feature, capture intent, write a spec, plan before coding, run a change from idea to production, onboard an existing repo to a governed process, add stage gates to CI, or turn a production incident back into backlog work. Trigger phrases include "start a feature", "capture intent", "write a spec", "plan before coding", "run this through the SDLC", "add a stage gate", "enforce our process", "close the loop on this incident".

Code & Development 10 stars 3 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# AI-Native SDLC Take a change from idea to production as a **loop around the agent**, not a linear human relay. Each stage **ends by committing one machine-readable artifact**, and the next stage **begins by reading it**. The chain of commits becomes the audit trail: who asked for what, what the agent produced, and who approved it. ``` Plan -> intent.md Design -> spec.md Build -> plan.md -> diff + tests Test -> a verification target + evals/ Deploy -> PR + REVIEW.md findings -> gated release Maintain -> bands.yaml breach -> writes a new intent.md (loop closes) ``` ## Instructions 1. **Identify the stage.** Read `.sdlc/active` for the current slug; artifacts live in `intent/<slug>/`. If there is no active slug, the work starts at Stage 1. 2. **Read the input artifact before producing the output artifact.** Never write `spec.md` without reading an accepted `intent.md`, and never edit source before `plan.md` is accepted. 3. **Run the gate rather than judging by eye:** ```bash python3 scripts/sdlc_gate.py intent/<slug> <design|build|test|deploy> # exit 0 = gate open, exit 2 = gate closed (reason on stderr) ``` 4. **Write the verification target BEFORE the implementation**, run it, and confirm it FAILS. A test that has only ever been seen green is not evidence. 5. **Implement, then re-run it until green.** If the implementation departs from `plan.md`, update `plan.md` in the same commit. 6. **Commit the artifact at the end ...

Details

Author
timwukp
Repository
timwukp/agent-skills-best-practice
Created
6 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ai-native-sdlc

Run the AI-native SDLC on any project, in any language. Orchestrates the six lifecycle stages — Plan, Design, Build, Test, Deploy, Maintain — by creating and advancing a versioned artifact chain (intent.md → spec.md → plan.md → diff → review.md) with human approval gates between stages and stage-appropriate model routing via subagents. Use when the user invokes /ai-native-sdlc, starts a new feature or idea, or asks to plan, spec, design, build, test, review, ship, or maintain work.

0 Updated 1 weeks ago
fahadakmal
Code & Development Solid

sdlc

Run an artifact-driven software lifecycle where each stage commits a markdown artifact that triggers the next - intent.md, spec.md, plan.md, verified diff, reviewed PR, monitored production. Use when the user asks to capture an idea as intent, write a spec, plan before implementing, set up a verification loop, define review policy, add agent-config evals, or wire production alerts back into the loop.

36 Updated 4 days ago
artemnovichkov
Code & Development Listed

spec

Run the AI-native software lifecycle. An intent arrives as a GitHub Issue, a Jira ticket, typed text or a file; it is classified against the repo's living spec at .claude/productizer/spec.md (extend, refine, duplicate, or contradict), merged as a spec delta, then planned and built. Use whenever the user starts a new feature, idea, bug or change and wants it done properly end-to-end; asks to capture an intent, update the spec, write an implementation plan, CLAUDE.md, review policy, approval gate, eval suite or control bands; asks whether something is already specified or contradicts existing requirements; asks how to adopt Claude across an SDLC or make agentic development governable and auditable; or asks what stage a piece of work is in and what comes next; or asks to SEE the pipeline, the spec, the fleet across repos, or a control band, which is published as a read-only view. Also use when wiring the lifecycle to GitHub Issues or Jira — picking a source of truth, binding a repo or project key, or moving tick

0 Updated 2 days ago
gitayg