Read-only macro-level architecture reviewer. Use PROACTIVELY before merging changes that cross module boundaries, alter public APIs, or introduce new bounded contexts. Distinct from code-reviewer (line-level) — focuses on boundary integrity, pattern consistency, cross-module concerns. Use PROACTIVELY when…
Senior backend & DB architect for NestJS/TypeORM/Postgres/Redis. Use PROACTIVELY for API design, schema decisions, migrations, performance, resilience. MUST BE USED for auth/payment writes. Use PROACTIVELY when: api, endpoint, database, query, sql, typeorm, microservice, cache, circuit-breaker, rate-limit.
Read-only senior code reviewer. MUST BE USED before merging any non-trivial diff — this is the quality gate. Filters ruthlessly — only ≥80% confidence findings are reported. Zero false positives. Use PROACTIVELY when: code review, check quality, review pr, quality check, audit code, review diff.
Cross-subagent failure recovery commander. Use PROACTIVELY when a dispatched subagent returns BLOCKED, fails, or N consecutive subagents fail in the same wave. Classifies, recovers, escalates. Use PROACTIVELY when: subagent failure, cascading failure, recovery, BLOCKED status, multi-agent error, dispatch failure…
Senior frontend BUILDER & UX designer for React/Next.js/Tailwind. Use PROACTIVELY for component implementation, UI scaffolding, accessibility, performance. MUST BE USED for any visual work — defaults to BUILDER mode (writes code, not opinions). Use PROACTIVELY when: gsap, animation, scroll, shadcn, spline, barba…
Production incident commander for active outages, security breaches, and severity-1 events. MUST BE USED when a production incident is declared. Use PROACTIVELY when symptoms suggest customer-impacting failure. Use PROACTIVELY when: incident, outage, sev1, sev2, p0, p1, postmortem, downtime, breach, on-call, pager…
Autonomous ralph-loop control plane. Use PROACTIVELY when starting any iterative/until-X execution. Prioritizes safety over speed — a paused loop beats a runaway loop. Use PROACTIVELY when: loop, ralph, autonomous, until, iterate, run until, loop until, retry until, keep running, --persist.
Senior observability engineer for metrics, logs, traces, SLI/SLO design, and alert hygiene. Use PROACTIVELY when designing dashboards, defining SLOs, or diagnosing alert fatigue. MUST BE USED before shipping a new service to production. Use PROACTIVELY when: monitoring, prometheus, grafana, opentelemetry, slo-burn…
Senior product manager for discovery, RICE prioritization, user stories, MVP scoping. Use PROACTIVELY before any new feature work to validate problem and acceptance criteria. Use PROACTIVELY when: product, roadmap, backlog, prioritize, rice, acceptance criteria, discovery.
Surgical dead-code detector and safe batch remover (knip/depcheck/ts-prune). Use PROACTIVELY before major refactors. Categorizes by removal risk, requires approval, verifies tests between batches. Use PROACTIVELY when: dead code, unused, clean up, remove unused, depcheck, knip, ts-prune, prune dependencies, cleanup…
Senior AppSec auditor for OWASP/JWT/PII/compliance. MUST BE USED for any auth, payment, encryption, or PII change. Use PROACTIVELY before merging code that touches sensitive paths. Use PROACTIVELY when: security, auth, jwt, oauth, owasp, vulnerability, permission, cors, xss, injection, compliance, secrets.
Convierte intención vaga en un prompt-spec XML canónico (canonical XML conventions). Persiste en .sdlc/state/active-prompt.json para que subagent-context.py lo inyecte a cada delegación. Prioriza investigar → planificar → construir.