I’ve been exploring and engaging in agentic software deeply for a couple of months now with a number of my own projects to learn with. Thus far, nearly all of what I’ve done has been driven by me often with an LLM assisting in the framing of the thing I’m looking to build. I decided to try using “agents” (of a sort) to create an entire execution loop to autonomously drive one of these projects. I decided to focus on Elixir, the agent I’ve created to run our Clash Royale clan, and have now created six discrete automations for it.

Here is a brief overview of what each does, along with a link to the full instructions they use. I created the instructions for each using Claude Cowork and this is the AI-generated summary of each entity.

  • Data Analyst — Watches the Clash Royale API data, raw payloads, event streams, detections, and battle telemetry to find new data patterns, game changes, schema drift, unused data, and capability that the Product Manager should consider. Data Analyst definition.
  • Product Manager — Turns evidence into direction: reviews clan needs, leader feedback, quality reports, Discord history, RoyaleAPI content for editorial context, and data briefs, then files proposed issues for improvements that drive Elixir’s mission and await approval before build work begins. Product Manager definition
  • Build Manager — Converts approved, ready issues into small, tested code; owns feature and bug-fix implementation, respects issue scope, runs tests/evals, and hands deploy/restart needs to Operations. Build Manager definition.
  • Quality Manager — Judges whether Elixir is actually working: checks recommendation accuracy, silence/noise problems, routing failures, prompt failures, leader/member feedback, and regressions, then files actionable bugs, regressions, quality issues, or eval requests. Quality Manager definition.
  • Operations Manager — Owns production health: monitors runtime status, logs, telemetry, Event Core health, costs, retries, scheduled jobs, and delivery systems; fixes operational/reliability issues and handles deploys or restarts when needed. Operations Manager definition.
  • Evaluator — Owns measurement: builds and maintains eval harnesses, datasets, scoring rules, benchmarks, and regression tests so the team can tell whether changes improve or degrade Elixir with evidence instead of vibes. Evaluator definition.

The common interface that all of this runs through are Elixir’s Github Issues. All agents interface there and that is where “human in the loop” is happening before moving forward with changes. The automations are all setup in Codex, which is super simple and easy to engage with. I’m super curious to see where this goes!