Read-only: do not create, edit, install, remove, configure, or write externally; reports never authorize implementation.
Workflow
- Confirm outcome, repo root, surface, and scope; read applicable
AGENTS.md/code_map.md. - Inventory relevant gates, roots, trusted config, plugins, and MCP. Prefer
structured tools or
rgand current help. - Summarize minimum fields, never raw doctor/config/auth/provider/env values.
Preserve provenance:
built-in,user-config,project-config,plugin-provided,installed-enabled,installed-disabled,available-uninstalled,unsupported,missing evidence. - Decide whether persistence is justified.
No change recommendedis valid. Smallest owner: one-off -> prompt; repo rule -> AGENTS; learned context -> memory; repeated flow -> skill; team bundle -> plugin; live external need -> MCP; independent role -> subagent; runtime default -> config/rule; lifecycle event -> hook; schedule -> automation. - Reuse suitable native/installed capability first. Technology detection alone is only a signal. Rank by impact, evidence, dependency, effort, reversibility, and Permission/data risk.
- Stop at supported decisions; keep OMX conditional and omit irrelevant surfaces.
Output Contract
Return Outcome; Evidence and Unknowns; supported Prioritized Recommendations;
dependency/risk Implementation Sequence; Verification and Rollback; and
Approval Options split by local versus persistent/external action. Each item:
Observed evidence; Existing capability/provenance; scope; prerequisites;
Permission/data risk; confidence or missing evidence; Verification;
Rollback/defer reason. Omit empty categories.
References
Load only relevant references. CLI help overrides examples and dated facts
override memory; otherwise use missing evidence.
Route direct AGENTS/code-map edits to agents-md-improver, fact questions to
openai-docs, skill reviews to agent-skill-review/yao-meta-skill, and
dynamic workflow builds to codex-dynamic-workflows.