-
Notifications
You must be signed in to change notification settings - Fork 0
Implement task assignment strategies (role-based, load-balanced, manual) #26
Copy link
Copy link
Closed
Labels
prio:mediumShould do, but not blockingShould do, but not blockingscope:medium1-3 days of work1-3 days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent SystemDESIGN_SPEC Section 3 - Agent Systemspec:communicationDESIGN_SPEC Section 5 - Communication ArchitectureDESIGN_SPEC Section 5 - Communication Architecturespec:company-structureDESIGN_SPEC Section 4 - Company StructureDESIGN_SPEC Section 4 - Company Structurespec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow EngineDESIGN_SPEC Section 6 - Task & Workflow Enginetype:featureNew feature implementationNew feature implementationtype:testTest coverage, test infrastructureTest coverage, test infrastructure
Description
Context
Implement pluggable task assignment strategies per spec section 6.4. Different situations call for different assignment approaches — sometimes a human specifies who should do the work, sometimes the system should auto-assign based on skills or workload.
Acceptance Criteria
Strategy Interface
- Pluggable strategy interface (`TaskAssignmentStrategy` abstract class)
- Strategy selection configurable per company or per project
Implemented Strategies (at least 3)
- Manual — explicit assignment by human or manager agent
- Role-based — match task requirements to agent skills/role
- Load-balanced — distribute tasks evenly across available agents
- Cost-optimized — assign to cheapest capable agent (stretch goal)
- Hierarchical — follow management chain for delegation (stretch goal)
Testing
- Unit tests for each implemented strategy
- Test that strategy interface is properly abstracted (easy to add new strategies)
Dependencies
- Depends on task decomposition and routing engine (Implement task decomposition and routing engine #14)
Design Spec Reference
- Section 6.4 — Task Assignment Strategies
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
prio:mediumShould do, but not blockingShould do, but not blockingscope:medium1-3 days of work1-3 days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent SystemDESIGN_SPEC Section 3 - Agent Systemspec:communicationDESIGN_SPEC Section 5 - Communication ArchitectureDESIGN_SPEC Section 5 - Communication Architecturespec:company-structureDESIGN_SPEC Section 4 - Company StructureDESIGN_SPEC Section 4 - Company Structurespec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow EngineDESIGN_SPEC Section 6 - Task & Workflow Enginetype:featureNew feature implementationNew feature implementationtype:testTest coverage, test infrastructureTest coverage, test infrastructure