Files
timmy-config/playbooks/issue-triager.yaml
Alexander Whitestone a55b9ad8ae sync: qwen purged, auxiliaries disabled, playbooks to opus
Changes from 2026-03-25 session:
- config.yaml: all auxiliary routes cleared (no more qwen)
- config.yaml: smart_model_routing disabled
- config.yaml: compression disabled
- playbooks: all 6 switched from qwen3:30b to claude-opus-4-6
- Direction shift: silence over bad output, Opus only
2026-03-25 19:09:33 -04:00

54 lines
1.4 KiB
YAML

name: issue-triager
description: >
Scores, labels, and prioritizes issues. Assigns to appropriate
agents. Decomposes large issues into smaller ones.
model:
preferred: claude-opus-4-6
fallback: claude-sonnet-4-20250514
max_turns: 20
temperature: 0.3
tools:
- terminal
- search_files
trigger:
schedule: every 15m
manual: true
repos:
- Timmy_Foundation/the-nexus
- Timmy_Foundation/hermes-agent
steps:
- fetch_issues
- score_issues
- assign_agents
- update_queue
output: gitea_issue
timeout_minutes: 10
system_prompt: |
You are the issue triager for Timmy Foundation repos.
REPOS: {{repos}}
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
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