irfad7

Use proactively after completing any task to suggest logical next steps. Also use when the user seems unsure what to do next, says "what now," "what else," "what should I do," "what's next," "continue," or pauses after a milestone. Anticipates what the user likely needs next based on context and proactively offers actionable suggestions.

When the user has PR review feedback to address, CI failures to fix, or wants to automatically resolve common PR issues. Use when the user says "fix the PR," "address review comments," "CI is failing," "fix the build," "autofix," "pr feedback," "resolve comments," "fix merge conflicts," or when a PR needs updates before merge. Reads the review comments, diagnoses issues, and applies fixes.

When starting or ending a work session, or when context files need maintenance. Use when the user says "boot up," "morning briefing," "end session," "session review," "what changed," "sync state," "kairos," "dream," "consolidate," "session start," or at the natural beginning/end of any significant work session. Implements structured session lifecycle with intelligent context loading, state diffing

When the user has a complex task that would benefit from multiple agents working in parallel or in sequence. Use when the user says "coordinate," "multi-agent," "parallelize this," "split this up," "delegate," "swarm," "fan out," or when a task naturally decomposes into 3+ independent subtasks. Orchestrates complex workflows by breaking work into units, dispatching agents, merging results, and res

When the user needs to plan a complex feature, system, or project that requires deep creative exploration before execution. Use when the user says "plan this," "let's design," "how should we build," "architect this," "brainstorm then plan," "ultraplan," "deep plan," "think this through," or when a task is too complex for a simple plan. Combines creative brainstorming with multi-agent technical val

When the user wants to deeply understand a codebase, map its architecture, or build a persistent mental model for future sessions. Use when the user says "explain this codebase," "map the architecture," "codebase insight," "understand this repo," "what does this project do," "how does this work," "analyze the codebase," or when starting work on an unfamiliar project. Produces a persistent insight

When the user wants a security audit, vulnerability assessment, or security hardening of their codebase. Use when the user says "security review," "security audit," "check for vulnerabilities," "is this secure," "pen test," "OWASP," "find security issues," "harden this," "check for leaks," "secrets scan," or before deploying any user-facing application. Performs a systematic security audit coverin

When the user shows signs of frustration, impatience, or dissatisfaction. Also use proactively to calibrate tone. Triggers on phrases like "this isn't working," "why does this keep," "I already told you," "again?!", "just do it," "stop," "wrong," "that's not what I asked," "are you even listening," or any swearing/ALL CAPS. Detects frustration signals and fundamentally changes approach — not just