// 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.
| 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. |
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.
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.
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
Recon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, then delegates execution to browser-explorer agent. Use when: "/browser-work", "브라우저 작업", "사이트에서 해줘", "웹에서 해줘", "LinkedIn에서", "크롬으로", "browser task", "automate this site".
Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearch, WebFetch, chromux browser-explorer, and Gemini CLI. Invoke with /deep-research <topic>.
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (chromux/CDP, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a validated plan.json and optional contracts.md. This adapter loads the canonical blueprint skill and follows its Codex runtime surface.