asdd
Use when a feature or substantial change should go from idea to shipped, verified software and an agent may run it for hours on its own — the ASDD (Agent Spec-Driven Development) dispatcher and front door, in any language. A spec that must prove itself, review inside every task scaled by `rsc risk`, a decision queue for what the agent must not decide alone. Routes constitution -> specify -> clarify -> plan -> tasks -> analyze -> implement (verify + review per task) -> closing -> ship. Successor of `sdd`. NOT a single phase (it dispatches), NOT small authorised changes (that is `ftd`), NOT the workspace harness (that is `harness`).
ericrisco · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add ericrisco/rsc-harness --skill asddAbout this skill
name: asdd
description: "Use when a feature or substantial change should go from idea to shipped, verified software and an agent may run it for hours on its own — the ASDD (Agent Spec-Driven Development) dispatcher and front door, in any language. A spec that must prove itself, review inside every task scaled by rsc risk, a decision queue for what the agent must not decide alone. Routes constitution -> specify -> clarify -> plan -> tasks -> analyze -> implement (verify + review per task) -> closing -> ship. Successor of sdd. NOT a single phase (it dispatches), NOT small authorised changes (that is ftd), NOT the workspace harness (that is harness)."
tags: [sdd, asdd, spec, workflow, plan, review]
recommends: [sdd-init, constitution, specify]
profiles: [core, full]
origin: risco
asdd — Agent Spec-Driven Development
The front door for letting an agent build for hours without coming back with a Frankenstein: intent in, shipped-and-verified software out, every decision recorded in 02-DOCS/wiki/sdd/.
Why it exists. Classic SDD reviewed at the end. On paper it checked the spec; in a long autonomous run, the only thing that bit for hours was the test — and tests prove the code works, not that it does what was asked (a real run: 8 hours, 4,500 green tests, and a dropped token plus a QR nobody requested). ASDD keeps the phases and changes two things: the spec must prove itself, and the review moves inside every task, scaled by risk. The human stops reviewing everything and only takes the decisions the agent must not take alone.
This skill does not do a phase. It names the method, reads the register, places the request on the map and hands off. Each phase skill points at the next one.
The five stages
request ─► decisor (answer · ftd · asdd)
│ asdd
1. BASE ─────► constitution + REVIEW.md (once per project)
2. SPEC ─────► specify (4 questions + out of scope) ─► clarify (gap checklist) ◄── HUMAN APPROVES
3. PLAN ─────► plan ─► tasks (criterion · risk forecast · check) ─► analyze
4. LOOP ─────► per task, in implement:
a build + self-check b rsc risk c review by tier
d verify findings e mandatory controls
f fix (max 3 rounds) g fix & record ─or─ park ─► DECISION QUEUE ◄── HUMAN
5. CLOSE ────► verify against main + rollback plan · closing review (whole branch vs spec) · explainer
SHIP ─────► remote: PR (self-merge only tier 0-1 + green CI + no blocking entry) │ no remote: park ◄── HUMAN
LEARN ────► finding outcomes · reverts → reviewer cases · repeated finding → rule
| Stage | Phase skills | Writes |
|---|---|---|
| 1 Base | ../constitution/SKILL.md (also drafts REVIEW.md), ../sdd-init/SKILL.md | constitution.md, REVIEW.md, config.yaml |
| 2 Spec | ../specify/SKILL.md → ../clarify/SKILL.md | specs/<slug>.md |
| 3 Plan | ../plan/SKILL.md → ../tasks/SKILL.md → ../analyze/SKILL.md | plans/<slug>.md, analysis/<slug>.md |
| 4 Loop | ../implement/SKILL.md, calling ../verify/SKILL.md and ../review/SKILL.md per task | progress/<slug>.md (with ## Decision queue), decisions.md |
| 5 Close | ../verify/SKILL.md (closing mode), then ../review/SKILL.md (closing review, on what will ship), ../ship/SKILL.md | verifications/<slug>-<date>.md, reviews/<slug>.md, the PR or parked branch |
| on demand | ../debug/SKILL.md · ../worktrees/SKILL.md · ../parallel/SKILL.md | — |
Where the human enters — three places only: approving the spec, answering the decision queue, approving a tier-2 merge. Everything else runs.
No ASDD phase edits the root CLAUDE.md: every artifact is indexed in 02-DOCS/wiki/index.md (the Knowledge map). The root CLAUDE.md is owned by harness and is tier 2 in rsc risk.
The spec proves itself
Every spec answers four questions, and spec:gate refuses one dated 2026-11-03 or later without them: what the user can do, what result they get (against a reference the human approved — a screenshot, a sketch, an expected API response), what it must respect (prior decisions, specs and behaviour; read from the brain when the project has one, else decisions.md), how it proves it (how the check runs, what evidence remains — "yes, I tested it" is not evidence). Plus an explicit out of scope: what the agent might add "just in case".
The risk decides, never the agent
npx @ericrisco/rsc risk [--base <ref>] [paths…] classifies a change by what it touches and what it adds (the sello's path table plus fixed content patterns — password hashing, session cookies, payments, schema changes, secrets — so auth code in src/app.js is still auth; works with the sello off): tier 0 docs/copy → no reviewer; tier 1 ordinary code → one fresh-context reviewer; tier 2 auth, billing, CI workflows, migrations, secrets, harness config → the three-refuter panel and human approval. An agent's approval never counts as a human's. Enforced at push: a tier-2 branch leaves the machine only with a spec linked to it that passes rsc spec gate and a panel recorded with rsc review ledger panel <slug>/<task> --lenses correctness,security,tests.
The loop converges
npx @ericrisco/rsc review ledger holds it to the rules that stopped Anthropic's 50-round reviews: round <slug>/<task> refuses a 4th round (rethink the approach or park the task), record marks a finding already raised as a repeat that is never raised again, outcome closes each finding as fixed|false|intentional|irrelevant, stats measures the noise. Flag the bug class, not the line; from round 2 re-review only the new diff.
Park, don't block
Tier 2, a contradiction with a recorded decision, a gap that would make the build unsafe, or no convergence in 3 rounds: the task goes to the decision queue (## Decision queue in `progress/<slug