ai-native-sdlc
SolidDrive 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".
Install
Quality Score: 82/100
Skill Content
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-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.
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.
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