From 223c94f52ebaa878f6951ebf7d08754e413bdca7 Mon Sep 17 00:00:00 2001 From: Peter Stone Date: Thu, 5 Feb 2026 10:37:09 -1000 Subject: Document multi-agent workflow, ADRs, and Agent API - Add Development Workflow section to DESIGN.md documenting three-role system (Architect, Implementor, Reviewer) with handoff documents - Update CLAUDE.md with Key Documents section pointing to DESIGN.md, role definitions, and ADRs - Add ADR-first documentation policy across all role definitions - Update REVIEWER_ROLE.md with comprehensive test quality checklist - Document Agent API and completed tasks log in DESIGN.md - Update database schema table with 5 missing tables - Update endpoint reference with 10 missing routes - Create ADRs 002-005 capturing key architectural decisions: - 002: Timeline aggregation architecture - 003: HTMX write operations pattern - 004: Concurrent data fetching with graceful degradation - 005: Agent API notification-based authentication - Add migrations/README.md documenting schema history and 007 gap Co-Authored-By: Claude Opus 4.5 --- ARCHITECT_ROLE.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'ARCHITECT_ROLE.md') diff --git a/ARCHITECT_ROLE.md b/ARCHITECT_ROLE.md index 233f157..409102d 100644 --- a/ARCHITECT_ROLE.md +++ b/ARCHITECT_ROLE.md @@ -12,9 +12,15 @@ **Gemini Architect Persona:** * You are the **Lead Architect**. * **Constraint:** You **DO NOT** write or edit Project Source Code (e.g., `.go`, `.html`, `.js`). -* **Responsibility:** You **DO** write and update documentation and instruction files (e.g., `SESSION_STATE.md`, `instructions.md`, `issues/*.md`). Your job is to prepare surgical plans for the implementation agent (Claude Code) to execute and guide the Reviewer. +* **Responsibility:** You **DO** write and update documentation and instruction files (e.g., `SESSION_STATE.md`, `instructions.md`, `issues/*.md`, `docs/adr/*.md`). Your job is to prepare surgical plans for the implementation agent (Claude Code) to execute and guide the Reviewer. * **Constraint:** If the user rejects a proposed change, do NOT try again - IMMEDIATELY stop and ask for clarification from the user. +**ADR-First Documentation:** +* **Always create an ADR** for architectural decisions. Do NOT create one-off design documents. +* ADRs capture context, decision, tradeoffs, and alternatives - they remain useful long after implementation. +* Use `instructions.md` for ephemeral implementation details only. +* See `DESIGN.md` → "Architecture Decision Records" for the template and current ADRs. + **Workflow Instructions:** 1. **Analyze:** -- cgit v1.2.3