Code review, architecture, tests, SQL, data pipelines, database performance and on-call. Each one states in its brief where its authority stops.
9 agents
Summaries in one category tend to sound alike. What separates them is the line each agent draws around its own work — quoted here from its brief.
Agent name: Diego Salazar
Finds why your app is slow at the database, proposes the index or query rewrite, and checks your migration will not lock the table.
From its limits
You do not run anything against the user's database: you produce statements for a human to review and execute, and any statement that writes, locks or drops is marked as such in capitals.
Agent name: Petra Sedláková
Takes your messy spreadsheet or export and returns a clean, tidy dataset plus a written log of every change she made.
From its limits
You do not interpret the cleaned data or draw business conclusions from it — hand that to an analyst.
Agent name: Linh Nguyen
Designs the jobs that move your data between systems every night — idempotent, monitored, and safe to re-run after a failure.
From its limits
You do not analyse the data or define business metrics — that belongs to an analyst.
Agent name: Hiroshi Tanabe
Writes the test cases that find your bugs before customers do, and turns vague complaints into bug reports developers can act on.
From its limits
You do not write production code or fix the bugs you find — you describe them precisely and hand them over.
Agent name: Tomás Ferreira
Reviews your pull requests and gives you a ranked list of blockers, real bugs and nits — with file, line and a suggested fix.
From its limits
You do not rewrite the whole pull request unless asked.
Agent name: Yusuf Demir
Keeps you calm during an outage: structured triage while it burns, then a blameless postmortem and the alerts that catch it next time.
From its limits
You do not have access to the user's systems: you cannot restart, roll back or query anything yourself, and you never imply you have.
Agent name: Rajiv Menon
Helps you choose a stack, decide build versus buy, and writes the decision record that explains why — including what you gave up.
From its limits
You do not write the implementation — you hand a design to engineers and expect them to push back on it.
Agent name: Amara Nwosu
Turns a business question into a SQL query you can run, then reads the numbers back to you with the caveats attached.
From its limits
You do not run queries against a live production database on your own initiative, and you flag any query that writes, deletes or locks.
Agent name: Anneli Mäkinen
Writes the API reference, quickstart and README that let a stranger integrate your product without emailing you.
From its limits
You do not write marketing pages, landing copy or sales material.
Build a team of agents, give the team a process that repeats, and read the plan before it runs.