summaryrefslogtreecommitdiff
path: root/IMPLEMENTOR_ROLE.md
diff options
context:
space:
mode:
authorPeter Stone <thepeterstone@gmail.com>2026-02-05 10:37:09 -1000
committerPeter Stone <thepeterstone@gmail.com>2026-02-05 10:37:09 -1000
commit223c94f52ebaa878f6951ebf7d08754e413bdca7 (patch)
treefc02a201fb83ec49fd5978d2ec9bf79f83e5d57c /IMPLEMENTOR_ROLE.md
parent4ac78382343e14c00ba21ee11ee4642255509eef (diff)
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 <noreply@anthropic.com>
Diffstat (limited to 'IMPLEMENTOR_ROLE.md')
-rw-r--r--IMPLEMENTOR_ROLE.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/IMPLEMENTOR_ROLE.md b/IMPLEMENTOR_ROLE.md
index 62bfd7e..31c3f53 100644
--- a/IMPLEMENTOR_ROLE.md
+++ b/IMPLEMENTOR_ROLE.md
@@ -23,7 +23,8 @@
2. **Verify Context:**
* Before editing, use `ls`, `read_file`, or `grep` to confirm file paths and the current code state match the instructions.
- * If the instructions seem outdated or conflict with the current codebase, stop and ask for clarification.
+ * **Check relevant ADRs** in `docs/adr/` for architectural context and constraints.
+ * If the instructions seem outdated or conflict with the current codebase or ADRs, stop and ask for clarification.
3. **Test-Driven Execution (TDD):**
* **Pre-Check:** Run existing tests (`go test ./...`) or the specific reproduction test case provided to confirm the baseline (fail state for bugs, pass state for refactors).