메뉴
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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/team-attention/hoyeon --skill hoyeon-execute명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| 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".