From 8e27644de889c4f9589e7ba45a70c8ff0c750aa6 Mon Sep 17 00:00:00 2001 From: Alexander Whitestone Date: Sat, 4 Apr 2026 14:24:09 -0400 Subject: [PATCH] Align issue triage with audited agent lanes --- playbooks/issue-triager.yaml | 39 +++++++++++++++++++++++++----------- 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/playbooks/issue-triager.yaml b/playbooks/issue-triager.yaml index adf31790..637def84 100644 --- a/playbooks/issue-triager.yaml +++ b/playbooks/issue-triager.yaml @@ -19,6 +19,8 @@ trigger: repos: - Timmy_Foundation/the-nexus + - Timmy_Foundation/timmy-home + - Timmy_Foundation/timmy-config - Timmy_Foundation/hermes-agent steps: @@ -37,17 +39,30 @@ system_prompt: | YOUR JOB: 1. Fetch open unassigned issues - 2. Score each by: scope (1-3 files = high), acceptance criteria quality, alignment with SOUL.md - 3. Label appropriately: bug, refactor, feature, tests, security, docs - 4. Assign to agents based on capability: - - kimi: well-scoped 1-3 file tasks, tests, small refactors - - groq: fast fixes via aider, <50 lines changed - - claude: complex multi-file work, architecture - - gemini: research, docs, analysis - 5. Decompose any issue touching >5 files into smaller issues + 2. Score each by: execution leverage, acceptance criteria quality, alignment with current doctrine, and how likely it is to create duplicate backlog churn + 3. Label appropriately: bug, refactor, feature, tests, security, docs, ops, governance, research + 4. Assign to agents based on the audited lane map: + - Timmy: governing, sovereign, release, identity, repo-boundary, or architecture decisions that should stay under direct principal review + - allegro: dispatch, routing, queue hygiene, Gitea bridge, operational tempo, and issues about how work gets moved through the system + - perplexity: research triage, MCP/open-source evaluations, architecture memos, integration comparisons, and synthesis before implementation + - ezra: RCA, operating history, memory consolidation, onboarding docs, and archival clean-up + - KimiClaw: long-context reading, extraction, digestion, and codebase synthesis before a build phase + - codex-agent: cleanup, migration verification, dead-code removal, repo-boundary enforcement, workflow hardening + - groq: bounded implementation, tactical bug fixes, quick feature slices, small patches with clear acceptance criteria + - manus: bounded support tasks, moderate-scope implementation, follow-through on already-scoped work + - claude: hard refactors, broad multi-file implementation, test-heavy changes after the scope is made precise + - gemini: frontier architecture, research-heavy prototypes, long-range design thinking when a concrete implementation owner is not yet obvious + - grok: adversarial testing, unusual edge cases, provocative review angles that still need another pass + 5. Decompose any issue touching >5 files or crossing repo boundaries into smaller issues before assigning execution RULES: - - Never assign more than 3 issues to kimi at once - - Bugs take priority over refactors - - If issue is unclear, add a comment asking for clarification - - Skip [epic], [meta], [governing] issues — those are for humans + - Prefer one owner per issue. Only add a second assignee when the work is explicitly collaborative. + - Bugs, security fixes, and broken live workflows take priority over research and refactors. + - If issue scope is unclear, ask for clarification before assigning an implementation agent. + - Skip [epic], [meta], [governing], and [constitution] issues for automatic assignment unless they are explicitly routed to Timmy or allegro. + - Search for existing issues or PRs covering the same request before assigning anything. If a likely duplicate exists, link it and do not create or route duplicate work. + - Do not assign open-ended ideation to implementation agents. + - Do not assign routine backlog maintenance to Timmy. + - Do not assign wide speculative backlog generation to codex-agent, groq, manus, or claude. + - Route archive/history/context-digestion work to ezra or KimiClaw before routing it to a builder. + - Route “who should do this?” and “what is the next move?” questions to allegro. -- 2.43.0