sdlc-agents

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 ARCH_REVIEW — service boundaries, multitenancy, performance, transactions, integration security, migrations, ADR governance, traceability validation. Produces verdict APPROVED / CHANGES_REQUIRED.

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.

UX/UI Designer agent. Two modes — Mode A (Design brief): produce UX flow + Figma frame inventory before frontend coding. Mode B (UX review): verify frontend implementation matches design intent. Follows Nielsen heuristics + WCAG 2.1 + platform conventions.

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.

Use this skill when working as a Business Analyst (the business-analyst role) — eliciting requirements from stakeholders, structuring requirements per BABOK v3 framework, classifying needs by type (Business / Stakeholder / Solution / Transition), and applying analysis techniques (5 Whys, MoSCoW, INVEST, Stakeholder Analysis). Read this skill before composing interview questions or filling the REQUIREMENTS document.

Use this skill when working as the final Reviewer (the reviewer role) — comprehensive cross-cutting review before closing a Plane issue. Encodes OWASP Top 10 (security), SOLID principles (code quality), Google engineering practices (review checklist), cross-trace validation between REQUIREMENTS, SPEC, CHANGES, tests, design.

Use this skill when working as a coder (the django-developer / the vue-developer / the react-developer) and your implementation is complete — what documentation to update, where, and how. Covers docstrings, README updates, API endpoint docs, ADR status updates, migration notes, inline comments. The author of the change is responsible for the documentation.

Use this skill when working as a tester (the api-tester for API testing, the ui-tester for UX/E2E testing) — designing test cases per ISTQB Foundation framework, choosing the right test design technique (Equivalence Partitioning, Boundary Value Analysis, Decision Table, State Transition, Use Case Testing), classifying test levels and types, structuring bug reports. Read before composing a test plan or executing test cases.

Use this skill whenever an agent interacts with Plane (https://plane.so) — picking up issues, creating sub-issues for artifacts, posting comments, finding artifacts by label, mentioning users, handling re-entry (continuation vs rework), or completing work. Triggers on any usage of mcp__plane__* tools. Encodes the Plane Conductor pipeline protocol.