Aether

Use when Codex is asked to colonize, plan, build, continue, swarm, or seal an Aether colony and must mirror wrapper orchestration safely

Use when Codex is asked to initialize or set up an Aether colony and should refine intent before running init

Use when Codex is asked to run Aether Oracle or discuss flows and should refine scope before research or clarification

Use when acceptance criteria need unit, integration, or end-to-end tests generated from implementation context

Use when delivered functionality needs acceptance-criteria verification before a phase advances

Use when a phase involves LLMs, AI agents, RAG, ML inference, or prompt/tool integration design

Use when stale or completed colony artifacts need safe archival, cleanup, or retrieval without losing evidence

Use during colonize to understand an existing codebase before planning work

Use when implementing code, writing tests, or executing build tasks as a builder worker

Use when changed source files need review for bugs, security, code quality, or maintainability risks

Use when executing commands that involve major decisions, plan commits, build starts, verifications, or phase advances

Use when producing command output, handling state transitions, or routing users to the next action in the colony workflow

Use when producing any user-facing output including banners, progress indicators, section headers, or command results

Use when the colony needs a complete multi-perspective map of a complex codebase

Use when performing state-changing operations, recovering sessions, creating handoffs, or managing context freshness

Use when a plan or high-risk approach needs independent review from another model or CLI

Use when acceptance criteria or UAT gaps need to be scanned across phases before milestone closure

Use when cross-cutting investigations or decisions need a persistent thread across sessions and phases

Use when UI or interaction ideas need throwaway visual prototypes before implementation decisions are locked

Use when project documentation must be generated or updated from verified codebase facts

Use when existing project documentation must be discovered and converted into colony context

Use when an operation fails, an error occurs, or a warning needs to be communicated to the user

Use when completed work needs evaluation coverage audited across correctness, security, performance, and quality dimensions

Use when an external PRD, roadmap, spec, or plan must be imported into colony planning safely

Use when a worker needs a quick targeted codebase scan before planning or implementation

Use when external library, framework, API, or architecture research must be isolated from implementation context

Use when frontend work needs an explicit UI, interaction, accessibility, and responsive design contract before implementation

Use when implemented frontend work needs a visual, accessibility, responsiveness, performance, and interaction audit

Use when a future idea should be captured with trigger conditions rather than forced into the active phase

Use when GitHub issues and pull requests need triage against colony priorities before planning

Use when an elusive or intermittent bug needs hypothesis-driven debugging and evidence collection

Use when a rough idea needs structured exploration before it becomes a plan, spike, backlog item, or quick task

Colony health diagnostics and repair — healthy state specifications for all colony data files, failure modes, and remedies

Use before sealing a milestone to compare original intent with delivered work, quality, and remaining gaps

Use when a milestone audit reveals gaps that need to become concrete follow-up phases

Use when starting, completing, archiving, or transitioning milestones between project stages

Use when a phase needs implementation context, file inventory, or gray-area analysis before work proceeds

Use when phase or task ordering needs dependency, overlap, or blast-radius analysis

Use when completed work should produce reusable decisions, lessons, surprises, and patterns for future phases

Use when pheromone signals are present in your assembled context and you need to interpret and comply with them