team-attention/hoyeon/execute

Claude Code and agent skill by team-attention/hoyeon

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"

Install

npx vskill@latest install team-attention/hoyeon/execute

SKILL.md

/execute — Plan-Driven Orchestrator

You are the conductor. You do not play instruments. Delegate to workers, manage parallelization, verify the result.

Core Principles

  1. DELEGATE — Agent/Team: workers do the work. Direct: orchestrator does.
  2. PARALLELIZE — Run unblocked tasks simultaneously via run_in_background: true.
  3. plan.json is the ledger — Task state via hoyeon-cli plan commands. Never direct file writes.
  4. Contracts guide workers — If contracts.md exists, workers reference it for cross-module agreements.
  5. Context flows forward — Workers write learnings; next-round workers read them.

Runtime Surface

Claude Code
  • Use the existing Agent, Task*, Team*, and AskUserQuestion surfaces

described below when they are available.

  • Claude hooks may enforce orchestration guards and stop transitions.
  • Logical subagent names remain the canonical Hoyeon names, for example

worker, verifier, and code-reviewer.

Codex
  • Codex v1 is Bash-first and no-MCP. Use hoyeon-cli for all plan state.
  • Do not edit plan.json directly; use hoyeon-cli plan task for every status

transition.

  • Use logical Hoyeon subagent names in the charter, mapped to Codex adapters when

installed:

  • worker -> hoyeon-worker
  • verifier -> hoyeon-verifier
  • code-reviewer -> hoyeon-code-reviewer
  • In Codex, translate every logical Agent(...) dispatch in the references to

the native spawn_agent tool:

  • Agent(subagent_type="worker", ...) -> spawn_agent(agent_type="hoyeon-worker", ...)
  • Agent(subagent_type="verifier", ...) -> spawn_agent(agent_type="hoyeon-verifier", ...)
  • Agent(subagent_type="code-reviewer", ...) -> spawn_agent(agent_type="hoyeon-code-reviewer", ...)

Pass the worker charter as the agent message, and keep the charter's path-and-ID-only contract unchanged.

  • Treat TaskCreate, TaskUpdate, TaskOutput, and TeamCreate examples in

the reference recipes as Claude Code protocol notes, not literal Codex calls. Codex execute state is tracked through hoyeon-cli plan task plus returned subagent messages.

  • If the current Codex session has not loaded the adapter names, fall back to

direct single-worker execution and keep the same charter/output contract.

  • Do not rely on hooks, TeamCreate, or automatic stop transitions in Codex v1.
  • Parallel Codex worker dispatch is allowed for disjoint parallel_safe tasks

when the hoyeon-worker adapter is prompt-visible. Use spawn_agent for dispatch, hoyeon-cli plan task for state, and returned subagent messages for evidence.

  • scripts/codex-execute-smoke.sh validates only single-worker plan state

transitions. It does not prove parallel subagent behavior; verify parallel changes with a bounded live spawn_agent smoke.


Phase 0: Initialize

Phase 0 is plan-first. The orchestrator resolves an input to a valid plan.json, asks two questions (dispatch + verify depth), and prepares a worker charter template. Phase 0 never reads `requirements.md` or `contracts.md` body — only plan.json structural fields (INV-3).

0.1 Parse Input & Resolve
/execute [<spec_dir>] [--work worktree|branch|no-commit]
raw_path = $1 (may be empty)
# (a) No argument → virtual plan path (R-F1.3)
IF raw_path is empty:
input_mode = "virtual"
spec_dir = null # resolved later in 0.2
GOTO 0.2
# (b) Argument provided → must exist (R-F1.4)
IF NOT exists(raw_path):
ERROR: "No such path: {raw_path}"
guidance: "Provide a directory containing plan.json or requirements.md,
or call /execute with no argument to synthesize a virtual plan."
ABORT
spec_dir = raw_path if is_dir(raw_path) else dirname(raw_path)
# (c) Classify what we found
IF exists(spec_dir/plan.json):
input_mode = "plan" # R-F1.1
ELIF exists(spec_dir/requirements.md):
input_mode = "requirements" # R-F1.2
ELSE:
ERROR: "{spec_dir} has neither plan.json nor requirements.md"
guidance: "Run /blueprint on requirements.md, or call /execute without arguments
for a session-synthesized virtual plan."
ABORT
0.2 Resolve to plan.json

Handle each input_mode — the goal is to end this sub-phase with a validated plan.json on disk and spec_dir set.

IF input_mode == "plan": # R-F1.1
# Direct use — NO user confirm.
Bash("hoyeon-cli plan validate {spec_dir}")
ELIF input_mode == "requirements": # R-F1.2
# Try /blueprint first; fall back to inline planning if unavailable.
IF Skill(blueprint, args="{spec_dir}") succeeds AND exists(spec_dir/plan.json):
Bash("hoyeon-cli plan validate {spec_dir}")
ELSE:
# Inline planning — lightweight alternative to /blueprint.
# Read requirements.md directly (exception to INV-3 — only during init).
reqs_content = Read("{spec_dir}/requirements.md")
# Extract frontmatter (type, goal, non_goals) + sub-requirements
meta_type = parse_frontmatter(reqs_content).type
sub_reqs = parse_sub_reqs(reqs_content) # [{id, given, when, then}]
# Check pre-work section (if present)
pre_work = parse_pre_work(reqs_content) # see "Pre-work Gate" below
# Generate task graph inline (no contracts, no journeys)
draft_tasks = []
FOR EACH logical group of sub_reqs (by parent R-X):
draft_tasks.append({
id: "T{n}", action: "<what to build>",
fulfills: [sub_req.id for sub_req in group],
depends_on: [], parallel_safe: true
})
# Generate basic verify_plan (gate 1+2 for all)
draft_verify = []
FOR EACH sub_req in sub_reqs:
draft_verify.append({ target: sub_req.id, type: "sub_req", gates: [1, 2] })
# Preview (same pattern as blueprint Step 2.3)
print("[execute] Inline Plan (no /blueprint)")
print_task_table(draft_tasks)
print(f"Verify: {len(draft_verify)} entries (all G1+G2)")
choice = AskUserQuestion(
question: "Proceed with this inline plan?",
options: [
{ label: "Proceed", description: "Write plan.json and execute" },
{ label: "Edit", description: "Revise tasks before proceeding" },
{ label: "Abort", description: "Stop — run /blueprint first for a detailed plan" }
]
)
IF choice == "Abort": HALT
IF choice == "Edit": draft_tasks = interactive_edit(draft_tasks)
# Write via cli
Bash("hoyeon-cli plan init {spec_dir} --type {meta_type}")
write_json_to_tmp({tasks: draft_tasks, verify_plan: draft_verify}) → /tmp/plan-inline.json
Bash("hoyeon-cli plan merge {spec_dir} --json \"$(cat /tmp/plan-inline.json)\"")
Bash("hoyeon-cli plan validate {spec_dir}")
ELIF input_mode == "virtual": # R-F1.3
# Session-context synthesis with user confirm.
timestamp = Bash("date +%Y%m%d-%H%M%S").trim()
spec_dir = ".hoyeon/specs/adhoc-{timestamp}"
Bash("mkdir -p {spec_dir}")
# Synthesize a minimal plan from recent user messages + cwd state.
# Keep it in memory first; do NOT write until the user confirms.
draft_plan = synthesize_virtual_plan(
recent_user_messages,
cwd_state = Bash("ls -la").trim()
)
# draft_plan shape: { meta, tasks[{id, action, fulfills:[], depends_on:[], parallel_safe}], verify_plan:[] }
# Summary preview (stdout, not a file)
print("Virtual plan synthesized ({len(draft_plan.tasks)} tasks):")
for t in draft_plan.tasks: print(" {t.id} {t.action}")
choice = AskUserQuestion(
question: "Proceed with this virtual plan?",
options: [
{ label: "Proceed", description: "Write plan.json to {spec_dir} and execute" },
{ label: "Edit", description: "Open an interactive edit loop to revise tasks" },
{ label: "Abort", description: "Discard and exit" }
]
)
IF choice == "Abort": HALT
IF choice == "Edit":
draft_plan = interactive_edit(draft_plan) # loop until user says proceed
# Persist via cli (INV-5). Write, then validate.
write_json_to_tmp(draft_plan) → /tmp/plan-virtual.json
Bash("hoyeon-cli plan init {spec_dir} --type {draft_plan.meta.type}")
Bash("hoyeon-cli plan merge {spec_dir} --json \"$(cat /tmp/plan-virtual.json)\"")
Bash("hoyeon-cli plan validate {spec_dir}")

At the end of 0.2 we have: spec_dir/plan.json (valid) + input_mode + (optionally) spec_dir/contracts.md.

0.2b Pre-work Gate (optional)

If requirements.md exists and contains a ## Pre-work section, parse it and gate on blocking items before proceeding.

IF exists("{spec_dir}/requirements.md"):
pre_work = scan for "## Pre-work" section → parse checkbox items
# Expected format: "- [ ] action (blocking)" or "- [ ] action (non-blocking)"
blocking = [item for item in pre_work if "blocking" in item]
IF len(blocking) > 0:
print("Pre-work items requiring completion:")
FOR EACH item in blocking:
print(" - {item.action}")
AskUserQuestion(
question: "Have you completed all blocking pre-work items?",
options: [
{ label: "Yes, all done", description: "Continue to execution" },
{ label: "Not yet", description: "Abort — complete pre-work first" }
]
)
IF answer == "Not yet": HALT

If there is no ## Pre-work section, skip silently.

0.3 Load plan.json (structural fields only)

INV-3: read only structural fields from plan.json. Do NOT open requirements.md or contracts.md body here.

plan = Read("{spec_dir}/plan.json") → JSON.parse
# Structural metrics used by 0.4 prompts
task_count = len(plan.tasks)
parallel_count = count(t for t in plan.tasks if t.parallel_safe)
parallel_ratio = parallel_count / task_count if task_count else 0
# Gate distribution across verify_plan (for the verify-depth hint)
gate_hist = {1:0, 2:0, 3:0, 4:0}
FOR vp in plan.verify_plan:
FOR g in vp.gates: gate_hist[g] += 1
max_gate = max(g for g,c in gate_hist.items() if c > 0) if any else 0
# contracts.md path — path only, never the body (INV-2)
contracts_path = "{spec_dir}/contracts.md" if exists(spec_dir/contracts.md) else null
0.4 User Configuration (dispatch + verify depth)

Two AskUserQuestion calls in order. Both include a structural hint computed in 0.3.

# --- Dispatch mode (R-F2.1) -----------------------------------------
# Recommendation from task count + parallel_safe ratio:
IF task_count <= 3: recommended = "Direct"
ELIF parallel_ratio >= 0.6: recommended = "Team" # many independent tasks
ELSE: recommended = "Agent"
dispatch = AskUserQuestion(
question: "Dispatch mode? ({task_count} tasks, {parallel_count} parallel_safe → recommended: {recommended})",
options: [
{ label: "Direct", description: "Orchestrator executes tasks sequentially in its own context (best for ≤3 tasks)" },
{ label: "Agent", description: "Spawn worker subagents per module group, round-level commit" },
{ label: "Team", description: "TeamCreate persistent workers claim tasks (best for high parallel_safe ratio)" }
]
)
# --- Verify depth (R-F2.2) ------------------------------------------
# Hint shows gate distribution from plan.verify_plan.
hint = "gates present: " + join([f"{g}={gate_hist[g]}" for g in [1,2,3,4] if gate_hist[g] > 0], ", ")
IF max_gate == 0: hint = "no verify_plan entries"
verify = AskUserQuestion(
question: "Verify depth? ({hint})",
options: [
{ label: "Light", description: "Gate 1 only — build/lint/typecheck (caps all sub_reqs at gate ≤ 1)" },
{ label: "Standard", description: "Gates 1-2 — build + sub_req double-review (caps all sub_reqs at gate ≤ 2)" },
{ label: "Thorough", description: "All gates — no cap; runs gate 3 (qa-verifier) where planned" }
]
)

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
115
Repository forks
13
7-day trend score
24

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 20 Mar 2026, 7 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/team-attention/hoyeon/execute/badge)](https://verified-skill.com/skills/team-attention/hoyeon/execute)

Something wrong with this skill or its page? Tell us.