Paranoid staff engineer code review mode. Finds bugs that pass CI but break in production. Use when user says /review, asks for code review, wants to check for bugs, or before merging important changes.
Founder/CEO product thinking mode. Challenges whether you're building the right thing. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when user says /plan-ceo, asks for product direction, or needs the 10-star version of a feature.
Engineering lead planning mode. Creates architecture, data flow diagrams, and technical specifications. Use when user says /plan-eng, needs technical planning, wants architecture review, or is about to implement a complex feature.
QA lead testing mode with browser automation. Tests affected pages, fills forms, takes screenshots. Use when user says /qa, wants to test the app, needs QA verification, or wants browser-based testing.
Research mode. Gathers domain knowledge, tech options, and best practices before planning. Use when user says /researcher, wants to research a feature/topic, or before /plan-ceo and /plan-eng for better-informed planning.
Engineering manager retrospective mode. Analyzes commit history, shipping velocity, and team contributions. Use when user says /retro, wants a weekly retrospective, needs to review what was accomplished, or wants team contribution analysis.
Release engineer execution mode. Handles git operations, runs tests, creates PRs. Use when user says /ship, wants to commit and push, needs to create a PR, or is ready to land their changes.
Step-by-step workflow orchestrator. Guides through feature, bugfix, or hotfix flows. Use when user says /workflow, wants guided flow, or needs to run researcher → plan-ceo → plan-eng → implement → review → ship → qa in sequence.