Menu
Use when Codex is asked to run Aether Oracle or discuss flows and should refine scope before research or clarification
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 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
| source | shipped |
| name | aether-colony-research |
| description | Use when Codex is asked to run Aether Oracle or discuss flows and should refine scope before research or clarification |
| type | colony |
| domains | ["aether","codex","oracle","research","clarification","prd"] |
| agent_roles | ["oracle","scout","architect","queen"] |
| workflow_triggers | ["oracle","discuss"] |
| task_keywords | ["aether oracle","oracle research","prd","research brief","discuss","clarification","requirements"] |
| priority | high |
| version | 1.0 |
Give Codex the wrapper-equivalent intelligence for oracle and discuss.
Codex should ask sharper questions, select the right Oracle template, and then
let the runtime own persistence and loop control.
For beginners: this is the part that turns "research this" into a focused brief before the Oracle starts working.
For Oracle:
aether command-guide oracle --platform codex
For discussion:
aether command-guide discuss --platform codex
Use command-guide as the source of truth. If it differs from this skill, follow
command-guide and update the skill.
If the user explicitly says raw, exact, no interview, no orchestration, or "just run this exact command", run the literal CLI command they provided. Say briefly that the Codex research synthesis layer was bypassed.
prdtech-evalarchitecture-reviewbug-investigationresearch-briefquick (5 iterations), balanced/standard (15), deep (30), or
exhaustive/marathon (50). Do not hide this behind a raw flag-only flow.
If the user gives an exact iteration cap, pass --max-iterations <1-50>.--confidence-target <percent>. Oracle should iterate until it reaches that
target, hits max iterations, or reports a hard blocker.AETHER_OUTPUT_MODE=visual aether oracle --depth <depth> --confidence-target <percent> --template <template> --background "<synthesized prompt>"
Use --background for long-running research, especially from OpenCode. The
runtime detaches a controller, writes progress under .aether/oracle, and
aether oracle status remains the inspection path. Omit --background only
when the user explicitly wants foreground execution.
For broad triage, prefer:
AETHER_OUTPUT_MODE=visual aether oracle --depth quick --confidence-target <percent> --template <template> "<focused triage prompt>"
If the shell/tool call times out, run aether oracle status before declaring
failure or switching to ad hoc agents.
If OpenCode subprocess dispatch is unavailable, let Oracle use its automatic
Codex/Claude fallback unless the user explicitly set AETHER_WORKER_PLATFORM=opencode.
AETHER_OUTPUT_MODE=json aether discuss-analyze --target .
AETHER_OUTPUT_MODE=visual aether discuss --resolve <id> --answer "<answer>"
discussion_status: settled, route back to aether plan..aether/data, Oracle output, pending decisions, or pheromone
files by hand.aether oracle status proves the runtime is blocked, stopped, or complete.cmd/command_guide.go together.