bootstraplisted

# bootstrap You are installing (or retrofitting) a documentation-led convention set in the current repo. The end state is a repo that can be driven by both humans and coding agents off a small set of canonical files. Carry over the *mechanism* described here — nothing about any other project. ## Step 1 — Detect the situation Inspect the repo before asking anything. - **Fresh repo** (no source, no docs): you are scaffolding from zero. - **Existing repo**: you are retrofitting. - Read any current `README.md`, `CONTRIBUTING.md`, `AGENTS.md`, `CLAUDE.md`, `docs/`, `adr/`, `.github/` before proposing changes. - Preserve existing content. Merge, don't overwrite. If existing conventions conflict with the ones below, surface the conflict in your assessment summary. - If ADRs already exist in another format, propose a migration plan (renumber, keep, translate) rather than creating a parallel tree. - **Already a docflow repo** (carries `AGENTS.md` + `CONVENTIONS.md` + an ADR catalogue): you are **adding to an existing setup**, not scaffolding. Do **not** re-scaffold the core or re-ask settled questions — read the recorded choices from `CONVENTIONS.md`/`AGENTS.md` (ADR shape, status lifecycle, **artefact root**, multi-agent mode, and which optional layers already exist). Then offer to **enable any opted-out optional layer** still absent — `plan/`, `_agent/`, `GLOSSARY.md`, `domains/`, or the technology-ADR template/split — and write only the chose