new-adrlisted
Install: claude install-skill EvolveHQ/docflow
# new-adr
Author one new ADR, consistent with this repo's conventions.
## Step 0 — Preconditions and context
1. Confirm the repo is bootstrapped: `AGENTS.md`, `CONVENTIONS.md`, and
an `adr/` directory with at least `adr/0000-template.md` must exist.
If not, stop and offer to run the **bootstrap** skill first.
2. Read `CONVENTIONS.md` to learn this repo's choices: ADR shape
(single vs. capability/technology split and the cutoff number),
status lifecycle, language mandate (if any), whether `domains/`
groupings exist, and the multi-agent mode.
3. Read `INDEX.md` and `ls adr/` to learn existing numbers and titles.
## Step 1 — Determine shape and number
- **Shape.** If the repo uses a single ADR shape, use
`adr/0000-template.md`. If it uses the split, decide capability vs.
technology from the user's intent (what the system must do →
capability; how it is built → technology); confirm with the user if
ambiguous. Use `adr/0000-template.md` (capability) or the technology
template (`adr/NNNN-template.md`).
- **Number.** Next contiguous integer after the highest existing ADR,
zero-padded to 4 digits. No gaps, no reuse. For a split repo, keep
capability ADRs below the cutoff and technology ADRs at/above it.
## Step 2 — Gather content
Ask for the pieces the chosen template needs, one prompt at a time:
- Title (sentence case), Context.
- Capability ADR: capability statement, user stories, **numbered,
testable** acceptance criteria.
- Technology ADR: de