Use when batch-delegating multiple independent tasks to Codegen cloud agents in a single call. Uses codegen_bulk_create_runs for parallel execution. Best for plans where tasks have no inter-dependencies.
Use when debugging failed, stuck, or misbehaving Codegen agent runs — systematic 4-phase approach. Triggers on agent run failures, timeouts, or unexpected results. Analogous to superpowers systematic-debugging but for cloud agents.
Use when reviewing code and PRs created by Codegen agents — two-stage review process. Stage 1 checks spec compliance (did the agent do what was asked?). Stage 2 checks code quality (is the code good?). Triggers after agent runs complete.
Use when analyzing Codegen agent run performance — interpret success rates, duration metrics, token usage, and trends via codegen_get_run_analytics. Best used after batch runs or for periodic performance review.
Guide for writing effective prompts for Codegen cloud agents. Includes templates, anti-patterns, and optimization strategies. Auto-triggers when creating agent runs to ensure prompt quality.
Monitor running Codegen agents — poll status, review logs, detect blockers, and surface progress. Triggered when codegen_get_run, codegen_get_logs, codegen_list_runs, or codegen_get_execution_context tools are invoked.
Automatically delegate tasks to Codegen cloud agents when user requests code changes, implementations, or fixes that should run remotely. Triggered when codegen_create_run or codegen_start_execution tools are invoked. Includes prompt templates and quality checklist.
Use when executing implementation plans via Codegen cloud agents instead of locally. Delegates each task as a separate Codegen agent run, monitors progress, and handles blockers. Drop-in replacement for superpowers:executing-plans — works with the same plan format.