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. State which situation applies in one line before asking the assessment questions. ## Step 2 — Target layout ``` <repo>/ AGENTS.md # hard rules for coding agents — entry point CLAUDE.md # one-liner: @AGENTS.md README.md # human-facing project summary (preserve if exists) CONVENTIONS.md # authoring rules: ADRs, naming, status, audit, git INDEX.md # generated table of all ADRs GLOSSARY.md # shared terms (optional — see Q7) adr/ 0000-template.md # capability-ADR template (al