Architecture decisions
An Architecture Decision Record (ADR) captures one significant decision — the context, the choice made, and its consequences — so the reasoning lives in the repo alongside the code. Decisions are immutable once accepted: to change one, add a new ADR that supersedes it.
Creating an ADR
Section titled “Creating an ADR”docslime add adr <short-slug>This creates the next-numbered record, e.g. 0001-<short-slug>.md. Fill it in (the file carries inline guidance), then add a row to the log below.
Status values
Section titled “Status values”- Proposed — under discussion.
- Accepted — decided and in effect.
- Superseded by ADR-NNNN — replaced by a later decision.
- Deprecated — no longer relevant.
Decision log
Section titled “Decision log”| ADR | Title | Status | Date |
|---|---|---|---|
| — | Skills-only execution (no server, no model calls from code) | Accepted, ADR pending | — |
| — | LLM-only quality gate (no deterministic validator) | Accepted, ADR pending | — |
| — | Handbook techniques summarized, not reproduced verbatim | Accepted, ADR pending | — |
| — | Install via vercel-labs skills CLI (skills/redteam/ is the installable artifact) |
Accepted, ADR pending | 2026-10-02 |
| — | package.json as single source of truth for version and repository owner (npm run sync / npm test) | Accepted, ADR pending | 2026-10-02 |