Receiving Code Review
Use to evaluate review feedback before changing code, especially unclear or suspect suggestions. Triggers on reviewer comments or requested changes. Not for requesting review.
Upgrading Megapowers
Use when asked to update, upgrade, refresh, or migrate Megapowers, check for a newer release, or discover new Megapowers plugins.
Council Adjudication
>-
Autonomous Run
>-
Executing Plans
Use to execute a written implementation plan inline with one writer, especially coupled tasks. Use subagent-driven-development for independent tasks with per-task review.
Golang Patterns
>
Cross Model Verification
>-
Effect Broker
>-
Humanizing Prose
Use to draft or edit user-facing docs, release notes, PRs, announcements, or errors. Triggers on "humanize", "sounds like AI", "slop", or "read naturally".
Multi Agent Delegation
>-
Systematic Debugging
Use to diagnose or fix bugs, failing or flaky tests, or unexpected behavior. Triggers on "why is this failing", "find the cause", "test suite is failing", or intermittent failures. Use TDD after finding the cause.
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Designing Frontends
>-
Using Git Worktrees
Use when starting feature work or an implementation plan that should verify or establish an isolated workspace. Reuse an existing worktree when suitable.
Using Megapowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before any response including clarifying questions
Typescript Patterns
>-
Greenfield Ts Stack
>-
Brainstorming
Use to design a feature, capability, or unclear behavior change. Triggers on "add a feature" or "figure out the approach". Use wayfinding when uncertainty blocks scoping. Skip mechanical edits and bug fixes.
Requesting Code Review
Use when finished work needs review before merge. Triggers on "review this", "ready to merge", or "check my work". Verify behavior first.
Dispatching Parallel Agents
Use for two or more independent tasks that can run concurrently in separate agents. Triggers on "parallelize", "fan out", or "agent for each". Not for dependent steps or shared state.
Verification Before Completion
Use before claiming work is complete, fixed, passing, ready to merge or publish, and before commits or pull requests. Triggers on any success or status claim.
Project Memory
>-
Writing Plans
Use when requirements need a multi-step plan before coding. Triggers on "write a plan", "break into steps", "save the plan", or "do not implement yet". Brainstorm unclear work first.
Orchestrating
>-
Wayfinding
Use when long-horizon work has unknown ownership, unresolved decisions, or unclear sequencing that prevents an honest specification or implementation plan.
Greenfield Go Stack
>
Python Patterns
>-
Finishing A Development Branch
Use when verified work needs branch integration or cleanup. Triggers on "work is done", "ship this", "merge or PR", or "wrap up the branch". Code review usually comes first.
Best Of N
>-
Greenfield Python Stack
>-
Subagent Driven Development
Use when a written plan has independent tasks for per-task subagent implementation and review. Triggers on "subagent per task", "subagent-driven", or "fan out plan tasks". Use executing-plans for inline work.
Test Driven Development
Use for any feature or bug fix. Triggers on "TDD", "test-first", "write the test first", "red-green-refactor", "implement and test", or requests to add code with tests. Diagnose unknown failures first.