setup-adrslisted

# Foundation ADRs Create the foundational Architecture Decision Record (ADR) sequence for a new project. ## When to Use - After running `bootstrap-project` skill - When establishing decision documentation for an existing project - When standardizing ADR practices across projects ## Required Inputs 1. **Project name** and description (from CLAUDE.md or user) 2. **Project type**: Development, Infrastructure, or Hybrid 3. **Technology stack** decision and rationale 4. **Development practices** to adopt (can use defaults) 5. **Operations requirements** (critical for Infrastructure projects) 6. **Project-specific constraints** or requirements ## Foundational ADR Framework Every project should have these foundational ADRs: | ADR | Purpose | Scope | Critical For | |-----|---------|-------|--------------| | ADR-0001 | HOW TO DECIDE | Decision methodology | All projects | | ADR-0002 | HOW TO DEVELOP | Development practices | All projects | | ADR-0003 | WHAT TECH | Technology stack | All projects | | ADR-0004 | HOW TO OPERATE | Operations practices | Infrastructure, Hybrid (optional) | **Note**: ADR-0004 is only needed for Infrastructure and Hybrid projects. Skip it for pure development projects (libraries, CLI tools, web apps without self-hosting concerns). ### Audience Traceability ADRs serve the **Contribution** audience category (maintainers, contributors, future architects). They provide the "understanding-oriented" content in Diátaxis terms, explaining *why* decisions