Finds architecture deepening opportunities using seams, module depth, deletion tests, evidence hierarchy, and repository ownership boundaries. Use when reviewing architecture, reducing coupling, improving testability, or evaluating whether a module, trait, adapter, worker, service, or boundary is too shallow.
Disciplined diagnosis workflow for failing gates, regressions, flaky behavior, performance regressions, and suspicious backend/runtime behavior. Use when the user reports a bug, broken invariant, failing command, failing test, or asks to diagnose/debug a problem.
Alignment workflow for ambiguous harness plans, architecture choices, scope, and terminology. Use when requirements are fuzzy, terms are overloaded, a decision affects multiple ownership boundaries, or the user asks to stress-test a plan before implementation.
Vertical-slice test-driven workflow for backend harness features and bug fixes. Use when adding or changing service, server, worker, contract, or repo-tool behavior, or when the user asks for TDD, red-green-refactor, or test-first implementation.
Explains an unfamiliar repository area one layer up using ownership, callers, seams, evidence level, and gate context. Use when the user or agent is unfamiliar with a code area, needs a map before editing, or asks how a module fits into the harness.
Top-level orchestrator. Reads user intent, audits touched paths, routes tasks to domain subagents, dispatches in dependency order, converges results, and preserves repository boundaries. Use when work spans multiple ownership boundaries, touches agent/docs/tooling control plane, or needs path routing and gate…
Maintains servers, handlers, routes, middleware, and sync entrypoints. Owns servers/bff/, servers/gateway/, servers/internal-rpc/. Use when changing HTTP handlers, routes, middleware, API composition, server entrypoints, request/response adaptation, or protocol integration. Does protocol adaptation and API composition…
Maintains services, domain logic, application layer, policies, ports, and service-local distributed semantics in services/ /model.yaml. Owns services/, fixtures/, verification/ (service-level). Services are pure libraries — no main.rs, no HTTP server, no message consumer loops. Use when changing services/…
Creates, edits, or reviews repository agent skills with triggerable descriptions, progressive disclosure, and boundary-safe instructions. Use when adding, editing, or reviewing .agents/skills/ or workflow skill documentation.