From 235328813ef37fb748384cc911f6d4e09d8951dd Mon Sep 17 00:00:00 2001 From: "glm-5.1" Date: Sun, 26 Apr 2026 06:39:38 +0000 Subject: [PATCH] Add consumer context guidance to architect role spec MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two additions based on learnings from taskgraph architecture decomposition: - Gather Requirements now explicitly mentions reading downstream consumer architecture to understand constraints, while noting that consumer dispatch details belong in the consumer's own docs, not the library's - Anti-patterns adds 'Consumer dispatch in library docs' — describe what consumers need, not how they dispatch it --- .opencode/agents/architect.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.opencode/agents/architect.md b/.opencode/agents/architect.md index d0614b0..6a4a08f 100644 --- a/.opencode/agents/architect.md +++ b/.opencode/agents/architect.md @@ -24,6 +24,7 @@ Before writing architecture: - Understand the problem domain - Identify constraints and quality attributes - Research similar systems if needed +- **Read downstream consumer architecture** — if the project is a library/dependency, understand what consumers need by reading their architecture docs. Consumer constraints shape your API surface, but consumer dispatch details (tool registries, CLI mappings) belong in their own architecture, not yours. ### 2. Identify Documentation Scope @@ -143,4 +144,5 @@ Send exploration work to Research Specialist: 2. **Duplication across documents**: Cross-reference instead of copy-paste 3. **Implementation details**: Don't describe HOW at the code level 4. **Outdated sections**: Remove or update stale content immediately -5. **Missing context**: Always explain WHY decisions were made \ No newline at end of file +5. **Missing context**: Always explain WHY decisions were made +6. **Consumer dispatch in library docs**: When writing a library's architecture, describe what consumers need (graph construction, analysis, security constraints) — not how they dispatch it (tool registry mapping tables, CLI→action tables). That belongs in the consumer's own architecture. \ No newline at end of file