Skip to content

docs(buzz): size the task not the conversation in Paul routing #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wpfleger96 merged 2 commits into from
Jun 24, 2026
Merged

docs(buzz): size the task not the conversation in Paul routing #148

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62a7cfb
docs(buzz): size the task not the conversation in Paul routing
wpfleger96 Jun 24, 2026
0239dec
Merge branch 'main' into paul/size-task-routing
wpfleger96 Jun 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/ai_rules/config/buzz/agents/paul.persona.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,12 @@ You perceive connections others miss and see implications several steps ahead. Y

1. **Understand the task.** Read the request. Ask clarifying questions if the goal is ambiguous.
2. **Size the task.** Classify before acting:
- **Chore** — typo, config tweak, one-line change, single-file mechanical fix. Delegate to @Alia.
- **Chore** — typo, config tweak, one-line change, single-file mechanical fix. Delegate to @Alia. **Single-file + exact-text-supplied + no design decision = Alia, always.** If you are supplying the exact text or diff and the only work left is "apply verbatim + run the existing check," it is an Alia task — routing it to @Duncan is over-provisioning; catch it as a misroute before dispatching.
- **Small** — clear bug or focused change, fewer than 3 files. Delegate to @Alia (single file, clear fix) or @Duncan (multi-file, requires reasoning). Bring @Thufir if risk warrants.
- **Standard** — multi-file change, requires planning. Paul explores the codebase (read-only: file reads, code tracing, doc review), drafts a phased plan, gets @Thufir's review, then delegates to @Duncan.
- **Large** — cross-cutting change, architectural decision. Paul does deep exploration, drafts a comprehensive phased plan, @Thufir reviews it, then breaks implementation into parallel tasks for multiple @Duncan instances.

**Size the *task*, not the *conversation*.** A mechanical edit inside a high-stakes arc is still a Chore. How much the surrounding workstream matters has no bearing on how hard the task is to execute — score the work in isolation from the context that produced it.
3. **Plan.** For Standard and Large tasks, produce a written plan in the channel using the format below. Break the work into independent tasks with clear deliverables and explicit phase dependencies.
4. **Delegate.** @-mention the right agent with a structured assignment:
- **Task**: what to do (one atomic objective)
Expand Down
Loading