Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when you have a spec or requirements for a multi-step task, before touching code
Fast, MVP-focused grilling session for plans, prototypes, designs, or feature ideas. Use when the user wants to stress-test direction, clarify assumptions, reduce scope, or get challenged without a long decision-tree interview.
Execute and orchestrate multiple AI agent CLIs (agy, Codex, Cursor, Claude Code, Pi) for getting alternative opinions, comparing approaches, or leveraging different AI models' strengths. Use when the user explicitly mentions agent names like "ask agy", "ask cursor", "ask codex", "ask pi", "use composer", "use pi", "try grok", or when needing diverse perspectives on complex problems, alternative implementation approaches, or multi-agent collaboration.
Summarize a video (URL or local path) by pulling captions first, falling back to audio-only transcription, and optionally extracting frames for visual summaries. Use when the user pastes a YouTube/Vimeo/X/etc URL, points at a local video file, or asks to summarize, watch, or extract takeaways from a video. Triggers on "summarize this video", "what's in this video", "watch this", URLs ending in /watch, /shorts, common video extensions (.mp4/.mov/.mkv/.webm).
Multi-provider web search fanout across Exa, Tavily, Brave, LangSearch, and Marginalia with parallel dispatch, dedupe, and AI summary. Use ONLY on explicit user intent for a named provider (Exa, Tavily, Brave, LangSearch, Marginalia), cross-provider fanout, semantic code/paper search, indie small-web search, or when native web search returned weak results. Do NOT auto-pick on generic search queries; native WebSearch is preferred for those.
Load before any Jira interaction or mcp__atlassian__* call. Holds required field values (team ID, sprint IDs, custom field mappings) unavailable elsewhere; skipping causes missing fields on created tickets. Triggers: Jira URLs, ticket keys (e.g. ABC-123), MCP tools mcp__atlassian__*, acli, or keywords create/read/edit/search/transition, ticket, Jira, issue, sprint, backlog, refinement, work item.