hoyeon-execute

SkillDev tools

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.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the hoyeon-execute skill

What this skill tells your AI

The instructions your AI receives, as published by team-attention/hoyeon in codex/skills/hoyeon-execute/SKILL.md and read by ahel’s review.

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:

  1. Read the canonical skill file above before executing the workflow.
  2. Follow the Runtime Surface -> Codex section in that file.
  3. Mutate task state only through hoyeon-cli plan task.
  4. Do not edit plan.json directly.
  5. Do not rely on hooks, MCP, or Claude TeamCreate for Codex v1.
  6. Use Hoyeon native-agent adapter names when dispatching subagents:
    • worker -> hoyeon-worker
    • verifier -> hoyeon-verifier
    • code-reviewer -> hoyeon-code-reviewer
  7. 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>")
  8. Treat canonical Agent(...), TaskCreate, TaskUpdate, TaskOutput, and TeamCreate examples as Claude Code protocol notes, not literal Codex calls.
  9. 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.

Signals

GitHub stars
174
Forks
24
Last commit
May 2026
Advanced
Catalog kind
skill
Gateway key
hoyeon-execute
Source
github.com/team-attention/hoyeon