architect
Analyze codebase architecture, classify dependencies, detect patterns and anti-patterns, and generate Architecture Decision Records. TRIGGER when: user asks about architecture, dependency analysis, ADRs, coupling, or wants to understand how a codebase is structured. DO NOT TRIGGER when: user wants a code review of specific files (use code-review), or wants to fix a bug (use focused-fix).
Repository SourceNeeds Review
performance-profiler
Profiling and optimization across languages in the polyglot stack. TRIGGER when: user asks about performance profiling, flamegraphs, benchmarks, load testing, memory leaks, or optimizing slow code paths in Node.js, Python, Go, Elixir, or Rust. DO NOT TRIGGER when: database-specific optimization (use database-designer), or build/bundle size issues without runtime perf concern.
Repository SourceNeeds Review
prd-to-plan
Convert a PRD into a phased implementation plan using tracer-bullet vertical slices, then optionally create GitHub issues from the plan. TRIGGER when: user has a PRD and wants an implementation plan, says "plan this", asks to break a feature into phases, wants to convert requirements into tasks, asks to break a PRD into issues, create issues from a plan, or says "prd to issues". Also when user wants to stress-test a plan, get grilled on their design, or says "grill me". DO NOT TRIGGER when: user wants to execute a plan (just code it), review existing code, or do general architecture discussion without a PRD.
Repository SourceNeeds Review
qa
Bug triage and issue creation. Single-issue investigation with TDD fix plans, or interactive multi-bug QA sessions with background codebase exploration. TRIGGER when: user reports a bug, unexpected behavior, or regression; wants to triage an issue; wants to run a QA session; says "qa session"; or asks to create an issue for a bug. DO NOT TRIGGER when: user wants to fix a bug (use focused-fix), or wants a code review of a PR (use code-review).
Repository SourceNeeds Review