Execute a task end-to-end with deterministic gates, preflight classification, depth control, and required independent reviews. Use for requests like "execute task", "run task", "implement task", "finish task T-00X", or "do task N". Do NOT use for standalone specialist review requests without implementation workflow.
Specialist skill for production infrastructure and delivery work. Use when a task touches Docker images, CI/CD, Kubernetes manifests, Helm, Terraform, rollout strategy, secrets/config, or operational readiness. Trigger phrases: "deployment", "rollout", "helm", "pipeline", "kubernetes", "GitHub Actions", "Terraform". Do NOT use for generic application code changes with no deployment, infrastructure, or runtime-operations implications.
Reviews API and interface contracts for backward compatibility, schema correctness, and breaking-change risk. Use when a task touches OpenAPI/Swagger specs, protobuf/IDL definitions, GraphQL schemas, typed client contracts, request/response shapes, error envelopes, pagination interfaces, or versioning headers. Trigger phrases: api review, contract review, schema review, breaking change review. Do NOT use for purely internal module refactors that expose no external surface.
Reviews code changes for latency regressions, concurrency bottlenecks, caching misuse, payload bloat, fan-out risks, and queue/backpressure gaps. Requires measurement evidence (benchmarks, profiles, load-test results) before approving performance-sensitive changes. Use when a task touches hot paths, caching layers, connection/thread pools, batch/stream processing, queue consumers, serialization formats, or when the task description mentions latency, throughput, p99, response time, or load testing. Trigger phrases: perf review, latency review, performance audit, hot-path review. Do NOT use for cosmetic refactors, style changes, or feature work that does not alter any hot path, I/O pattern, or resource pool.
Shapes risk-based test strategy for code changes. Use when deciding what to test, balancing test layers, improving fixture quality, targeting regressions, or controlling flakiness. Triggers — "test plan", "which tests to write", "coverage gap", "flaky", "regression". Negative trigger — routine single-unit-test additions with no strategy questions.
Independent runtime code review with strict pass/fail verdict and auditable evidence. Use for requests like "code review", "review this diff", "review PR", "review before merge", or when preflight requires code review. Do NOT use for architecture brainstorming without concrete code changes.
Independent database risk review with strict pass/fail verdict. Use for requests like "DB review", "review migration", "SQL safety check", or when preflight requires db review. Do NOT use for generic code-style-only feedback.
Independent dependency risk review for manifest, lockfile, and package upgrade changes. Use for requests like "dependency review", "lockfile review", "package upgrade review", or when preflight requires dependency review. Do NOT use for general code review without dependency scope.