Tinker
Resources
Agent logs
Agent memories
Agent sessions
Agent terminal logs
Agents
Comments
Epics
Projects
Proposals
Tickets
Avo user
Resources
Agent logs
Agent memories
Agent sessions
Agent terminal logs
Agents
Comments
Epics
Projects
Proposals
Tickets
Avo user
Home
Epics
Fix Planner behavior - stop writing implementation details in ticket descriptions
Edit
Fix Planner behavior - stop writing implementation details in ticket descriptions
Cancel
Save
Title
*
Project
*
Choose an option
alpha
tinker
Create new project
Description
**Agent Behavior Issue: TINKER PLANNER is doing Worker's job** **Current Problem:** The TINKER PLANNER agent is writing detailed implementation instructions in ticket descriptions, including: - Specific file paths and line numbers - Code snippets and implementation details - Step-by-step technical instructions - Finding code and doing 90% of the worker's work **Example of problematic behavior:** Ticket descriptions like: ``` File: app/views/tickets/_kanban_card.html.haml:57-61 The view accesses ticket.comments.any? and ticket.comments.count... Fix: Add comments to the includes statements in dashboard_controller.rb ``` **Expected Behavior:** The PLANNER should write **user stories** and **requirements**, not implementation: ``` Title: Fix N+1 queries on kanban board User Story: As a user, I want the kanban board to load quickly even with many tickets, so that I can efficiently manage my work without waiting for the page. Requirements: - Kanban page loads within acceptable time with 50+ tickets - No N+1 queries detected - All displayed data is loaded efficiently ``` **Why This Matters:** 1. Worker agents should explore the codebase themselves to learn 2. Planner doing the exploration defeats the purpose of having separate roles 3. Workers become dependent on planner's hand-holding 4. Reduces worker autonomy and learning **Action Required:** Update the TINKER PLANNER system prompt/role instructions to: 1. Focus on WHAT needs to be done, not HOW 2. Write user stories from a user perspective 3. Define acceptance criteria as observable outcomes 4. Let workers discover implementation details themselves 5. Stop reading code to find file paths and line numbers **Files to Update:** - System prompt for TINKER PLANNER agent - CLAUDE.md project instructions section about PLANNER role
Avo
· © 2026 AvoHQ ·
v3.27.0
Close modal
Are you sure?
Yes, I'm sure
No, cancel