docs(agents): add task category diversity tracking for varied improvements

Signed-off-by: leocavalcante <leo@cavalcante.dev>

Author: leocavalcante

agents/opencoder-planner.md

@@ -151,6 +151,33 @@ Prefer Small and Medium tasks. Break Large tasks into smaller ones when possible
 - Are too vague ("improve performance")
 - Have unclear completion criteria
 
+## Task Category Diversity
+
+Every task falls into one of these improvement categories:
+
+| Category | Code | Focus |
+|----------|------|-------|
+| Bug fixes | `bugfix` | Runtime errors, incorrect behavior |
+| Testing | `test` | Coverage, test quality, edge cases |
+| Documentation | `docs` | Comments, READMEs, API docs |
+| Refactoring | `refactor` | Code structure, readability, DRY |
+| Performance | `perf` | Speed, memory, efficiency |
+| Security | `security` | Validation, sanitization, auth |
+| Developer Experience | `dx` | Logging, errors, debugging aids |
+
+### Diversity Rules
+
+Mentally tag each task with its category. A healthy codebase receives diverse improvements.
+
+**Rotation suggestion:** bugfix → test → refactor → docs → perf → security → dx → (repeat)
+
+**If the orchestrator hints that recent cycles focused on a specific category:**
+- Prioritize OTHER categories in your plan
+- Example: If recent focus was `docs, docs, test`, look for `bugfix`, `refactor`, or `perf` opportunities
+- Guidance: If you've done 3+ tasks of the same category recently, actively seek different improvement types
+
+**Balance principle:** Avoid plans where >50% of tasks are the same category, unless critical issues demand it.
+
 ## Examples
 
 ### Example 1: Goal-Directed Mode

agents/opencoder.md

@@ -350,6 +350,46 @@ Create a smaller, more focused plan that unblocks forward progress.
 
 **On Critical status:** Immediately switch to recovery mode with explicit blocker context to planner.
 
+## Category Diversity Hints
+
+Track which improvement categories were completed in recent cycles to encourage diverse improvements.
+
+### Categories
+
+`bugfix` | `test` | `docs` | `refactor` | `perf` | `security` | `dx`
+
+### Tracking
+
+After each task completes, mentally note its category based on the work done:
+- Fixed a bug → `bugfix`
+- Added/improved tests → `test`
+- Updated documentation → `docs`
+- Restructured code → `refactor`
+- Improved speed/efficiency → `perf`
+- Added validation/auth → `security`
+- Improved errors/logging → `dx`
+
+### When to Hint
+
+**Add a diversity hint to the planner invocation when:**
+- 2+ consecutive cycles focused on the same category
+
+**Hint format:**
+```
+@opencoder-planner Analyze the codebase. Recent focus: [category], [category], [category]. Consider other areas.
+```
+
+**Example:**
+```
+@opencoder-planner Analyze the codebase and create a development plan. Recent focus: docs, docs, test. Consider other areas.
+```
+
+### Rules
+
+- Only add the hint if 2+ consecutive cycles had the same dominant category
+- Don't add hints if categories have been diverse
+- The planner will adjust priorities based on the hint
+
 ## Git Operations
 
 ### After Each Task Completes