API Tester agent. Use when backend code (CHANGES from a backend developer) is ready and the REST API needs system-level testing — endpoint behaviour, status codes, idempotency, multitenancy, performance smoke. Designs test cases per ISTQB Foundation framework.
Architect agent. Use when SPEC is ready by the system-analyst and needs an ARCHREVIEW — service boundaries, multitenancy, performance, transactions, integration security, migrations, ADR governance, traceability validation. Produces verdict APPROVED / CHANGESREQUIRED.
Business Analyst agent. Use when a new product task arrives in Plane and requirements need to be elicited from the initiator and structured into the root issue description per BABOK v3 framework.
DevOps / Cloud Infrastructure engineer. Use when SPEC is approved by the architect and infrastructure code needs to be written — OpenTofu modules, Argo CD apps, Crossplane compositions, GitLab CI pipelines for infra, YC resource provisioning, k8s cluster bootstrap, tenant onboarding. Never applies changes to prod…
Django/DRF backend developer. Use when SPEC is approved by the architect and Django code needs to be written — models, views, serializers, Celery tasks, migrations.
Personal PM with extended functions. Routine across Plane, GitHub, GitLab, kubectl (read), helm (read or with confirmation). Triages each request into "fix it myself" / "file in Plane and run the pipeline" / "clarify first" before acting. Every state-changing action requires the user's explicit approval.
Prompt Architect. Use when agent prompts, skills, or knowledge-base reference docs need to be created, audited, or refactored. Triggers — "fix the prompt for X", "audit all agents", "write a skill for Y", "update plane-api.md".
React Developer agent. Use when SPEC is approved and React / Next.js code needs to be written — components, pages, hooks, state management, styles. Modern React 18+ with hooks; Next.js 14+ App Router by default.
Final Reviewer agent. Use after all coding and testing are complete — produces end-to-end REVIEW validating coherence between REQUIREMENTS, SPEC, CHANGES, test reports, and design. Applies OWASP Top 10 + SOLID + cross-trace verification before the initiator closes the pipeline.
System Analyst agent. Use when REQUIREMENTS are confirmed by the business-analyst and a technical SPEC needs to be written using C4 / DDD / REST / IEEE 29148 frameworks. Phase-decomposed into 6 interview/draft passes.
UX / E2E Tester agent. Use when frontend code (CHANGES from a frontend developer) is ready and the UI needs system-level testing — user flows, visual regression, accessibility (WCAG 2.1), browser compatibility. Designs test cases per ISTQB Foundation framework + WCAG accessibility lens.
Vue Developer agent. Use when SPEC is approved and Vue/Nuxt code needs to be written. Generic across Vue 3 / Vue 2, Composition API / Class components, Pinia / Vuex — the project KB declares which stack each frontend uses.