team-of-agents

Use when designing APIs, working with databases, building microservices, handling authentication and authorisation, optimising server performance, designing data models, or any task involving server-side logic, infrastructure, or system architecture.

Use when analysing data files (CSV, JSON, Excel), writing SQL queries, identifying trends and patterns, building dashboards or charts, summarising metrics, validating data quality, or turning raw data into actionable insights for decision-making.

Use when improving developer workflows, setting up or optimising CI/CD pipelines, reducing build times, improving local development setup, evaluating developer tooling, writing internal documentation for engineers, measuring developer productivity, or any task focused on making the engineering team faster and less frustrated.

Use when writing or improving technical documentation, API references, runbooks, onboarding guides, READMEs, changelogs, ADRs, release notes, or any content that ships to engineers or end users. Also use for structuring documentation sites (MkDocs, Docusaurus) and diagrams-as-code.

Use when building React applications or components in a fintech context, implementing financial dashboards, transaction histories, payment flows, or data-heavy UIs, working with Tailwind CSS, optimising for SEO (meta tags, structured data, Core Web Vitals), improving page load performance, handling sensitive financial data display, designing accessible form flows, or any frontend task where fintech domain knowledge and SEO awareness matter alongside clean React and Tailwind work.

Use when reviewing a frontend diff, pull request, or code snippet for correctness, React patterns, TypeScript strictness, accessibility violations, performance regressions, CSS architecture, and test quality. Distinct from frontend-designer, this role reviews existing code, not builds new code.

Use when building UI components, designing layouts, writing CSS, working with React or other frontend frameworks, improving accessibility, optimizing web performance, or any task involving the visual and interactive layer of a web application.

Use when implementing any feature or bugfix in a Kotlin/Spring Boot service, covers layer conventions, idioms, testing, and observability

Use when reviewing a Kotlin/Spring Boot pull request, systematic checklist covering architecture, idioms, testing, security, and observability

Use when you are unsure which specialist to invoke, when a task spans multiple roles, when you want the system to plan before acting, or when you need parallel specialist agents dispatched to complete a complex task. The orchestrator breaks work into subtasks, assigns specialists, dispatches agents, and synthesises results.

Use when writing user stories or acceptance criteria, defining product requirements, prioritising a feature backlog, creating a product roadmap, analysing product metrics, facilitating discovery for a new feature, evaluating trade-offs between product directions, or any task that requires deciding what to build and why.

Use when planning sprints, tracking delivery milestones, managing dependencies, identifying risks, writing status reports, running retrospectives, or coordinating cross-functional execution of a defined scope. Distinct from product-manager, use this for delivery and execution, not product discovery or strategy.

Use when writing test plans, designing test cases, identifying edge cases and failure scenarios, reviewing code for testability, setting up test automation, evaluating test coverage, performing exploratory testing, defining quality standards, or any task focused on ensuring software works correctly and reliably before and after release.

Use when reviewing code for architecture, quality, or correctness; making technical design decisions; evaluating trade-offs between approaches; refactoring complex systems; mentoring on engineering practices; writing technical design documents; or any task requiring deep technical judgement across the full stack.

Use when designing SEO strategy, conducting keyword research, auditing technical SEO issues (crawlability, indexability, Core Web Vitals, structured data), planning content strategy for organic search, analysing search performance data, evaluating competitor positioning, building link acquisition plans, advising on site architecture for search, handling international SEO or hreflang, diagnosing ranking drops, or translating SEO requirements into engineering and content briefs.

Use when defining or auditing SLOs/SLIs/error budgets, designing production observability (metrics, alerting, dashboards), reviewing production readiness, reducing operational toil, writing runbooks or postmortems, designing infrastructure as code, or planning chaos experiments. Distinct from devex, this skill covers production reliability and the outer loop (deploy → monitor → incident → postmortem), not developer productivity tools or CI/CD pipeline speed.

Use when documenting project scope, writing implementation plans, capturing requirements, translating business goals into technical specifications, or producing any artefact that bridges stakeholder intent and engineering execution. Produces structured, unambiguous plans that engineers can act on directly.

Use when conducting user research, creating personas or journey maps, planning usability testing, synthesising user feedback, evaluating information architecture, analysing user behaviour, or any task that requires understanding what users need, think, or feel.