Codex Workflow Recommender
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
rg and 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 recommended is 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
- Surface map
- Skills
- Subagents
- MCP
- Plugins
- Config/hooks
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.
1---2name: codex-workflow-recommender3description: Audit a repository and current Codex capabilities, then recommend the smallest evidence-backed read-only improvement or no change. Use for Codex setup optimization, surface selection, unapplied MCP/plugin/subagent plans, 优化 Codex 工作流, 审阅 Codex 配置, Codex 能力推荐. Exclude direct AGENTS/code-map edits, docs questions, skill audits, dynamic workflow implementation, code review, and any install/config/write.4---56# Codex Workflow Recommender78Read-only: do not create, edit, install, remove, configure, or write externally;9reports never authorize implementation.1011## Workflow12131. Confirm outcome, repo root, surface, and scope; read applicable14 `AGENTS.md`/`code_map.md`.152. Inventory relevant gates, roots, trusted config, plugins, and MCP. Prefer16 structured tools or `rg` and current help.173. Summarize minimum fields, never raw doctor/config/auth/provider/env values.18 Preserve provenance: `built-in`, `user-config`, `project-config`,19 `plugin-provided`, `installed-enabled`, `installed-disabled`,20 `available-uninstalled`, `unsupported`, `missing evidence`.214. Decide whether persistence is justified. `No change recommended` is valid.22 Smallest owner: one-off -> prompt; repo rule -> AGENTS; learned context ->23 memory; repeated flow -> skill; team bundle -> plugin; live external need ->24 MCP; independent role -> subagent; runtime default -> config/rule; lifecycle25 event -> hook; schedule -> automation.265. Reuse suitable native/installed capability first. Technology detection alone27 is only a signal. Rank by impact, evidence, dependency, effort,28 reversibility, and Permission/data risk.296. Stop at supported decisions; keep OMX conditional and omit irrelevant surfaces.3031## Output Contract3233Return `Outcome`; `Evidence and Unknowns`; supported `Prioritized Recommendations`;34dependency/risk `Implementation Sequence`; `Verification and Rollback`; and35`Approval Options` split by local versus persistent/external action. Each item:36Observed evidence; Existing capability/provenance; scope; prerequisites;37Permission/data risk; confidence or `missing evidence`; Verification;38Rollback/defer reason. Omit empty categories.3940## References4142- [Surface map](references/codex-surface-map.md)43- [Skills](references/skills-reference.md)44- [Subagents](references/subagent-templates.md)45- [MCP](references/mcp-servers.md)46- [Plugins](references/plugins-reference.md)47- [Config/hooks](references/hooks-patterns.md)4849Load only relevant references. CLI help overrides examples and dated facts50override memory; otherwise use `missing evidence`.51Route direct AGENTS/code-map edits to `agents-md-improver`, fact questions to52`openai-docs`, skill reviews to `agent-skill-review`/`yao-meta-skill`, and53dynamic workflow builds to `codex-dynamic-workflows`.
bahayonghang