Every stage has one skill. Every skill is one file.

Each skill is a single SKILL.md in the open Agent Skills format, read identically by Claude Code, Codex, Cursor, Gemini, Copilot, Windsurf and OpenCode. The CLI (npx aisdlc-cli) is the referee that derives state and enforces the gates; the skills are the behaviour.

stage: discover

aisdlc-brainstorm The front door for any new request.
aisdlc-brownfield Safe entry into an existing codebase.
aisdlc-discover Double-Diamond discovery intake for a new idea or feature in the standard or regulated lane.

stage: specify

aisdlc-spec Write or repair an EARS specification (spec.md) that passes `npx aisdlc-cli check spec`.

stage: plan

aisdlc-plan Produce plan.md with architecture, explicit decisions (alternatives, ponytail ladder rung), seams, work breakdown as tracer bullets, risks, and a Traceability table that maps every spec requirement to tasks, then request human G1 approval.

stage: tasks

aisdlc-tasks Generate or repair tasks.md from the plan's work breakdown so every task is a small tracer bullet, traceable to a requirement, checkable, and ordered by its blocking edges, then pass gate G2 (artifact consistency).

stage: build

aisdlc-craft Bridge to code-craft, the line-level clean-code discipline (the ladder before writing, smell→fix on touched lines only, dead-code deletion with dynamic-reference checks, honest types, rule of three).
aisdlc-debug Disciplined, evidence-backed debugging loop for bugs, flaky tests, performance regressions and "it works on my machine".
aisdlc-implement Implement one task at a time, test-first at the agreed seam, with the ponytail ladder applied, recorded evidence, and zero scope creep.

stage: verify

aisdlc-quality Bridge to code-quality-tools, the runner guide for lint, autofix, dead-code, complexity and security CLIs on JS/TS and Python (fallow, eslint, biome, knip, tsc, ruff, mypy, vulture, bandit, semgrep - which tool, in what order, what mutates vs detects).
aisdlc-verify Run the merge-safety gate G3 honestly - full test run recorded as evidence, secrets scan, and kind-specific verification (visual diff, a11y, integration smoke, dry-run, evals).

stage: accept

aisdlc-review Act as an independent reviewer for the acceptance gate G4 - a two-axis review (Spec axis: does the diff faithfully implement every scenario? Standards axis: does it follow the repo's taste, smell baseline and ponytail minimalism?) that audits evidence against each spec scenario, fills acceptance.md, files findings, and prepares the human sign-off.

stage: release

aisdlc-release Prepare and gate a release - rollout.md with strategy and rollback (G5, human approved), then guardrails.yaml and runbook.md for runtime budgets, kill switch and on-call actions (G6).
aisdlc-retro Close the loop on a finished feature, incident, or sprint so the process gets better instead of just longer.

cross-cutting

aisdlc-delta Handle any change of intent after the spec is signed - new requirement, changed behaviour, removed scope, a bug that reveals the spec was wrong.
aisdlc-flow The aisdlc router.
aisdlc-grill Relentless, structured interview that turns a vague plan, idea, spec, or design into shared understanding before anything is built.
aisdlc-handoff Compact the current session into a handoff document so a fresh session, a different agent, or a human can continue without loss.
aisdlc-ponytail Bridge to Ponytail, the "lazy senior developer" discipline that forces the simplest, shortest solution that actually works (YAGNI, stdlib before custom code, native platform before dependencies, one line before fifty).
aisdlc-taste Capture and apply a project's taste profile (code style, testing philosophy, agent verbosity, laziness level for the ponytail ladder, interview depth, review strictness, definition of done, UI design language) and seed the shared glossary.