| name | hoyeon-execute |
| description | Hoyeon execution workflow for Codex. Use when the user invokes
"$hoyeon-execute" or wants to execute a Hoyeon plan.json through the
Bash-first Codex adapter. This adapter loads the canonical execute skill and
follows its Codex runtime surface.
|
hoyeon-execute
This is the Codex-facing wrapper for Hoyeon's canonical execute skill.
Canonical skill:
- Installed root:
__HOYEON_PLUGIN_ROOT__/skills/execute/SKILL.md
- Repo-local fallback:
skills/execute/SKILL.md from the current Hoyeon repo
When this skill is invoked:
- Read the canonical skill file above before executing the workflow.
- Follow the
Runtime Surface -> Codex section in that file.
- Mutate task state only through
hoyeon-cli plan task.
- Do not edit
plan.json directly.
- Do not rely on hooks, MCP, or Claude
TeamCreate for Codex v1.
- Use Hoyeon native-agent adapter names when dispatching subagents:
worker -> hoyeon-workerverifier -> hoyeon-verifiercode-reviewer -> hoyeon-code-reviewer
- In Codex, dispatch those adapters with the native
spawn_agent tool:
spawn_agent(agent_type="hoyeon-worker", message="<worker charter>")spawn_agent(agent_type="hoyeon-verifier", message="<verification charter>")spawn_agent(agent_type="hoyeon-code-reviewer", message="<review charter>")
- Treat canonical
Agent(...), TaskCreate, TaskUpdate, TaskOutput, and
TeamCreate examples as Claude Code protocol notes, not literal Codex calls.
- Parallel worker dispatch is allowed for disjoint
parallel_safe tasks when
the relevant adapter is prompt-visible. scripts/codex-execute-smoke.sh
validates plan state transitions only, not parallel subagent behavior.
The output contract remains the canonical Hoyeon contract:
all executable tasks completed or blocked with evidence, followed by plan
validation.
