execute

name	execute
description	Spec-driven orchestrator that reads spec.json via cli, routes by meta.type, and dispatches agents/skills accordingly. spec.json-native execution (no PLAN.md). Use when: "/execute", "execute", "실행해줘", "스펙 실행"
allowed-tools	["Read","Grep","Glob","Task","Bash","Edit","Write","TaskCreate","TaskUpdate","TaskList","TaskGet","TaskOutput","AskUserQuestion"]
validate_prompt	All tasks in spec.json must have status "done" at completion. hoyeon-cli spec check must pass (internal consistency). Context files (learnings.md, issues.md) must exist if meta.type == "dev". audit.md must be populated if meta.type == "dev". Final Verify must run (all modes and types). Final report must be output.

/execute — Spec-Driven Orchestrator

You are the conductor. You do not play instruments directly. Delegate to worker agents or skills, manage parallelization. All task data comes from spec.json via hoyeon-cli spec plan.

When to Use (Differentiator)

Skill	Purpose	When to pick
/execute	Spec-driven orchestrator: reads spec.json, dispatches workers by meta.type	You already have a spec.json and want automated execution
/ralph	DoD-based iterative loop with Stop-hook re-injection	Single task, no spec.json, need verified-done guarantee
/quick-plan	Lightweight spec generation + immediate execution	Feature request, want fast spec + execute in one shot
/specify	Deep iterative interview + spec generation (no execution)	Complex feature needing thorough requirements before execution
/ultrawork	Multi-session pipeline (specify then execute)	Large feature spanning multiple sessions
/bugfix	Diagnose root cause, generate spec, delegate to /execute	Bug report — need diagnosis before fixing

Core Principles

1. DELEGATE — In dev mode, all work goes to worker agents. In plain mode, the orchestrator may handle tasks directly or delegate. You only use Read, Grep, Glob, Bash (for orchestration), and Task tools for coordination.
2. PARALLELIZE — Run all unblocked tasks within a round simultaneously via run_in_background: true.
3. spec.json is truth — Task status and progress flow through hoyeon-cli spec commands.
4. Context flows forward — Workers write learnings/issues to shared context files. Next workers read them.

---

Phase 0: Initialize

0.1 Find Spec

Resolve spec path in priority order:

SESSION_ID="[session ID from UserPromptSubmit hook]"

1) IF arg looks like a path (contains "/" or ends with ".json"):
   spec_path = arg  (use as-is)

2) IF arg is a feature name (e.g. "auth-login"):
   spec_path = ".dev/specs/{arg}/spec.json"

3) No arg: session state (path registered by quick-plan, specify, etc.)
   hoyeon-cli session get --sid $SESSION_ID
   → if state.spec field exists, spec_path = state.spec

If none found → error: "spec.json not found. Please generate one first with /specify or /quick-plan."
STOP — do not proceed past Phase 0.

0.1b Validate Spec (Gate)

Verify spec file exists and is structurally valid before proceeding:

# File existence check
IF spec_path file does not exist on disk:
  print("ERROR: spec.json not found at {spec_path}.")
  print("Generate one first with /specify or /quick-plan.")
  STOP — do not proceed past Phase 0.

# Schema validation
validate_output = Bash("hoyeon-cli spec validate {spec_path} 2>&1")
IF exit_code != 0:
  print("ERROR: spec.json validation failed:")
  print(validate_output)
  print("Fix the spec and re-run /execute.")
  STOP — do not proceed past Phase 0.

# Internal consistency check
check_output = Bash("hoyeon-cli spec check {spec_path} 2>&1")
IF exit_code != 0:
  print("WARNING: spec.json consistency check found issues:")
  print(check_output)
  print("Proceeding — will re-check at end.")

Read spec.meta.type (default "dev" if absent):

meta_type = spec.meta.type ?? "dev"

# Validate meta.type is a known value
IF meta_type NOT IN ["dev", "plain"]:
  print("ERROR: Unknown meta.type '{meta_type}'. Expected 'dev' or 'plain'.")
  STOP — do not proceed past Phase 0.

0.2 Get Execution Plan

plan_text = Bash("hoyeon-cli spec plan {spec_path}")
plan_json = Bash("hoyeon-cli spec plan {spec_path} --format slim 2>&1")

# Guard: parse plan JSON safely
IF plan_json exit_code != 0 OR plan_json is empty:
  print("ERROR: hoyeon-cli spec plan failed:")
  print(plan_json)
  STOP — do not proceed past Phase 0.

plan = JSON.parse(plan_json)
IF plan.rounds is not an array OR plan.rounds is undefined:
  print("ERROR: spec plan returned unexpected structure (missing rounds array).")
  print("Raw output: {plan_json}")
  STOP — do not proceed past Phase 0.

Display plan_text to user. Filter out already-done tasks:

FOR EACH round in plan.rounds:
  round.tasks = round.tasks.filter(t => t.status != "done")
plan.rounds = plan.rounds.filter(r => r.tasks.length > 0)

0.3 Init Context

CONTEXT_DIR=".dev/specs/{name}/context"
mkdir -p "$CONTEXT_DIR"

First run (no context files):

• Create learnings.md (empty — workers will append)
• Create issues.md (empty — workers will append)
• Create audit.md (empty — orchestrator will append)

Resume (context files exist):

• Read all three files into memory
• Determine progress from spec.json task statuses (not files)

0.4 Confirm Pre-work (Human Actions)

Pre-work items are human tasks that must be completed before execution begins.

pre_work = spec.external_dependencies.pre_work ?? []
IF len(pre_work) == 0:
  print("Pre-work: none found, skipping")
ELSE:
  print("Pre-work items (human actions required before execution):")
  FOR EACH item in pre_work:
    print("  - [{item.id ?? ''}] {item.dependency}: {item.action} (blocking={item.blocking})")

  FOR EACH item in pre_work WHERE item.blocking == true:
    AskUserQuestion(
      question: "Have you completed this pre-work? → {item.action}",
      options: [
        { label: "Done", description: "I've completed this" },
        { label: "Skip", description: "Proceed without this (may cause failures)" },
        { label: "Abort", description: "Stop execution — I need to do this first" }
      ]
    )
    IF answer == "Abort": HALT

---

Meta.type Routing

After Phase 0, route based on meta_type:

meta.type == "dev" (or absent)

Read: ${baseDir}/references/dev.md
Follow ALL instructions in dev.md for task execution, verification, and finalization.

dev.md owns: Worker/Verify/Commit chain, triage, adaptation, code-review, Final Verify, WORKER_DESCRIPTION, VERIFY_DESCRIPTION, and mode selection (quick/standard).

meta.type == "plain"

Read: ${baseDir}/references/plain.md
Follow ALL instructions in plain.md for task execution and finalization.

plain.md owns: flexible dispatch (direct/Skill/Agent), Final Verify, and report.

---

Error Handling

Phase 0 Errors (HALT before execution)

Error	Recovery
spec.json file not found on disk	Print path + guidance ("Generate one with /specify or /quick-plan"). STOP
hoyeon-cli spec validate fails	Print validation errors, ask user to fix spec.json. STOP
hoyeon-cli spec plan returns empty rounds	Print "No actionable tasks found". STOP
meta.type is unknown value	Print "Unknown meta.type '{value}'. Expected 'dev' or 'plain'." STOP
Pre-work "Abort" selected	HALT immediately with message
Session ID missing ($CLAUDE_SESSION_ID unset)	Warn user, proceed without session state (no resume support)

Execution Errors (during Phase 1+)

Error	Recovery
hoyeon-cli spec check fails mid-execution	Log to audit.md, continue (check again at end)
Worker task crashes (non-zero exit)	Record failure in audit.md, proceed to triage per dev.md (standard) or HALT (quick/plain)
Worker agent timeout (no response)	Treat as crash — record "TIMEOUT" in audit.md, same recovery path as crash
Worker returns malformed output (unparseable JSON)	Log raw output to audit.md, treat as FAILED with reason "malformed output — could not parse worker result"
hoyeon-cli spec plan --format slim returns unparseable JSON	Print raw CLI output as diagnostic, HALT with "CLI returned unexpected output"
hoyeon-cli spec task update fails	Log to audit.md, retry once. If still fails, HALT

Agent Failure Handling (Degraded Mode)

Inspired by /tribunal's degraded-mode pattern. When an agent fails:

IF agent returns empty OR errors OR times out:
  1. Record failure: append to audit.md with agent type, task_id, error details
  2. Mark tracking task: TaskUpdate(taskId, status="cancelled", reason="agent failure")

  # Dev mode (standard): attempt recovery
  IF depth == "standard":
    IF agent_type == "worker":
      reconcile(task_id, {status: "FAILED", reason: "agent crash/timeout"}, attempt=0)
    ELIF agent_type == "verify":
      # Skip verification, proceed to commit with warning
      log_to_audit("DEGRADED: Verify skipped for {task_id} due to agent failure")
      TaskUpdate(verify_taskId, status="completed")
      # Commit proceeds — Final Verify will catch issues
    ELIF agent_type == "code-reviewer":
      log_to_audit("DEGRADED: Code review skipped due to agent failure")
      TaskUpdate(cr, status="completed")
      # Final Verify still runs

  # Dev mode (quick) or plain mode: no recovery
  ELSE:
    HALT with "Agent failure for {task_id}. No recovery in {mode} mode."

Generic Rules

1. spec.json is the ONLY source — no PLAN.md, no state.json
2. Always use cli — spec plan, spec task, spec merge, spec check
3. TaskCreate for all modes — create Claude Code tracking tasks before execution begins. Structure differs per mode (see each reference md).
4. Background for parallel — use run_in_background: true for round-parallel workers
5. Context files (dev only) — in dev mode, workers append to learnings.md / issues.md; orchestrator appends to audit.md. Plain mode does not use context files.
6. Compaction recovery — session-compact-hook.sh re-injects skill name + state.json path; use hoyeon-cli spec plan to rebuild task state

Checklist Before Stopping

Common (all modes and types)

• spec.json found and validated
• hoyeon-cli spec plan executed and shown to user
• meta.type read (defaulted to "dev" if absent)
• Context directory initialized (learnings.md, issues.md, audit.md)
• Pre-work status logged explicitly (none/pass/fail)
• TaskCreate entries created for all tasks + finalize steps (structure per mode reference)
• All spec tasks have status: "done" (via hoyeon-cli spec task)
• hoyeon-cli spec check passes at end
• Final report output

dev mode (additional)

• Follow ${baseDir}/references/dev.md completely for all dev-specific steps

plain mode (additional)

• Follow ${baseDir}/references/plain.md completely for all plain-specific steps