codex/skills/hoyeon-execute/SKILL.md
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.
npx skillsauth add team-attention/hoyeon hoyeon-executeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is the Codex-facing wrapper for Hoyeon's canonical execute skill.
Canonical skill:
__HOYEON_PLUGIN_ROOT__/skills/execute/SKILL.mdskills/execute/SKILL.md from the current Hoyeon repoWhen this skill is invoked:
Runtime Surface -> Codex section in that file.hoyeon-cli plan task.plan.json directly.TeamCreate for Codex v1.worker -> hoyeon-workerverifier -> hoyeon-verifiercode-reviewer -> hoyeon-code-reviewerspawn_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>")Agent(...), TaskCreate, TaskUpdate, TaskOutput, and
TeamCreate examples as Claude Code protocol notes, not literal Codex calls.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.
development
Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.
development
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
testing
"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변 기록", "요구사항 명확화", "설계 명확화". Relentless ambiguity-resolution interview that records Q&A under .hoyeon/clarify/<topic>/ and hands off to specify/blueprint/docs when clear.
development
Hoyeon requirements workflow for Codex. Use when the user invokes "$hoyeon-specify" or wants to turn an unclear goal into structured requirements.md for Hoyeon. This adapter loads the canonical specify skill and follows its Codex runtime surface.