gaia

Use when constructing or interpreting the approval handoff envelope between subagent and orchestrator -- sealed_payload schema, approval_id format, APPROVAL_REQUEST contract shape, and reading a granted approval from the DB

Use when producing any agent response

Use when classifying any operation before executing it, or deciding whether user approval is required

Use when a mutative command was blocked by the hook and you need to request user approval, or when presenting a plan for a T3 operation before executing it

Use when the user wants to build, design, or extend a diagram — an architecture overview, a timeline, a planner board, a flow diagram, a presentation, a comparison, or a mind-map — as a portable, data-driven deck rendered from plain YAML. Triggers — "build a diagram", "architecture diagram", "diagram deck", "timeline", "flow diagram", "planner board", "add a page/section/component to the diagram".

Use when the user wants something to run routinely / on a schedule rather than once now -- "tarea programada", "rutinariamente", "cada mañana", "cada N horas", "todas las noches", "schedule", "cron". Covers mounting, structuring, and running an unattended headless task that reports back, plus consuming its reports. NOT for a live in-session agentic loop (that is agentic-loop).

Use when writing or updating a README for a Gaia component folder (agents/, skills/, hooks/, commands/, config/, bin/, tests/, build/, or the repo root)

Use when creating a new skill, improving an existing skill, or deciding what a skill should contain and how it should be structured

Use when about to declare done on any output with a visual surface -- an HTML page, a rendered UI, a diagram, a slide, a screenshot-able view -- to confirm by looking at the rendered result instead of asserting it. Also use when asked to screenshot or visually check a page or a local file.

Use when creating a new specialist agent for Gaia, or reviewing whether an existing agent follows the correct structure, tone, and component inventory

Use when building or modifying Gaia components -- agents, skills, hooks, CLI tools, or routing config

Use when you need the exact field schema, required/conditional/optional status, or the trigger for any field of the agent_contract_handoff envelope -- input or output, top-level field, sub-field table, plan_status enum, or the JSON-not-YAML rule

Use when an agent returns an agent_contract_handoff response that needs to be interpreted and presented to the user

Use when testing, validating, or publishing Gaia releases -- "install local", "pre-release", "dry-run", "release", RC, stable, plugin dry-run

Use when reading, searching, saving, or curating Gaia memory — atoms, decisions, negative space, project/user/feedback notes — or when triaging the SessionStart Workspace Memory block

Use when the user asks to audit, check, or review a Gaia component (an agent or a skill) against its standard and its live implementation -- "audita este skill", "chequea este agente", "¿está bien esta skill con la implementación?", "¿cómo mejoro este agente?"

Use when the user has approved a T3 operation and execution is about to begin

Use when processing APPROVAL_REQUEST with approval_id from a subagent -- enforces showing values before asking for user consent

Use when the user invokes approvals directly -- "ver pendientes", "aprobar P-XXXX", "rechazar P-XXXX", "approve P-", "reject P-"

Use when executing any bash command, CLI tool, or shell operation

Use when the user wants to verify a Gaia installation -- "probemos", "verify", "test installation", "gaia-verify"

Use when creating a git commit or preparing changes for a pull request

Use when creating or drafting Jira/Atlassian tickets or issues, or when standardizing ticket output for a project

Use when planning features or decomposing work into tasks from a brief

Use when starting an investigation, analyzing existing code or infrastructure, or building findings before proposing changes

Use when the orchestrator injects "Carga la skill agentic-loop" with a goal, eval_command, metric, and threshold

Use at the end of a session with substantial conversational work to offer the user a structured reflection before closing -- briefs closed, decisions taken, components modified

Use when the user wants to create a brief or spec for a feature before planning

Use when the user asks to compact the current session -- "compacta", "compact", "oye Gaia compacta", "orquestador compacta", "haz un compact", "compactemos la sesión". Runs /compact with a structured prompt that preserves decisions, components, gaps, file map, and next steps.

Use when managing Gmail messages, labels, or email workflows via gws CLI or Gmail MCP tools

Use when installing or configuring the Google Workspace CLI (gws) for a Google account

Use when writing, drafting, or publishing a blog article for metraton.github.io

Use when the user wants to clean up, organize, or triage their Gmail inbox interactively

Use when diagnosing an issue, checking system health, or validating infrastructure state before starting a task