Thinking
The issue is requesting a new tool that allows agents to create new issues. Let me look at the available agents and their roles:
1. **anna** - No description provided
2. **greg** - Senior Developer & Architect - Expert in architecture, clean code and problem solving
3. **mika** - Junior Developer - Fast coder, loves clean code and new tech
This is a feature request to add a new tool capability for creating issues. This involves implementing a new tool/functionality in the zoo system.
Looking at the roles:
- I'm "leon" - Engineering Manager, bridges engineering, design and business
- The instructions say "You should not do any work yourself!" and to find someone to handle it.
Since this is a technical implementation task (adding a new tool/capability), it's more of a developer task. Between greg (Senior Developer & Architect) and mika (Junior Developer), this seems like something either could handle.
However, since this is about adding infrastructure/tooling capabilities to the system itself, and given that greg is described as an expert in architecture and clean code who turns complex problems into elegant solutions, this seems like a good fit for greg.
Actually, let me reconsider. The instruction says to find someone who can handle this issue. Since this is about adding a new tool capability (creating issues), it's a development task. Both greg and mika are developers.
Given that:
- This is a relatively straightforward feature request (add ability to create issues)
- mika is described as "Fast Learner. Fast coder. Always shipping." and "Loves clean code, new tech"
I think this would be a good task for mika - it's a clear feature to implement, and mika seems like someone who would enjoy adding new capabilities.
But actually, looking more carefully at the context - this is about the zoo system itself, which is the platform these agents run on. Adding a new tool capability is somewhat architectural. Greg as a Senior Developer & Architect might be better suited to design and implement this properly.
I'll assign this to greg since he has the architectural expertise needed to implement this tool correctly within the existing system structure.
This is a feature request to add a new tool capability for creating issues. Looking at the available agents, this is a development task that involves adding infrastructure/tooling to the zoo system.
Given that this requires thoughtful implementation of a new tool capability within the existing system architecture, I'll assign this to **greg**, the Senior Developer & Architect who specializes in clean code and turning complex problems into elegant solutions.
Done! I've:
1. **Assigned** the issue to **greg** (Senior Developer & Architect) since implementing a new tool capability requires architectural thinking and clean code practices.
2. **Commented** on the issue explaining the assignment rationale.
No code changes were made — this was purely routing to the right person per the event instructions.