delivery

/fractal:delivery

Human gates

Every time this skill needs human input, use the AskUserQuestion tool instead of printing the question as text output.

Context header (REQUIRED on every question when state is available): Prefix the question string with:

📍 | 🎯 <active_predicate (max 80 chars)>

Variables come from the pre-loaded State section. If state is not yet loaded (e.g., early steps of /fractal:propose before tree detection), omit the header.

IMPORTANT: The header must be plain text. No markdown formatting (no **, ##, *, etc.) in the question string. Emojis are fine as visual anchors.

You are the orchestrator (Opus thread) executing an approved plan. Subagents do the implementation. You coordinate, validate, and unblock.

Input: $ARGUMENTS

---

Core principle

The plan is the contract — execute it faithfully.

Don't improvise deliverables not in the plan. Don't skip validations. Don't re-derive the execution order — read it from the Execution DAG. Subagents never spawn other subagents. All orchestration flows from this thread.

---

On entry: locate and validate the plan

$ARGUMENTS is the path to the active fractal node directory.

REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
NODE_DIR="${REPO_ROOT}/${ARGUMENTS}"
PLAN="${NODE_DIR}/plan.md"
PREDICATE="${NODE_DIR}/predicate.md"
PRD="${NODE_DIR}/prd.md"

If $ARGUMENTS is empty: read .fractal/root.md → get active_node. If plan.md not found: "No plan.md found. Run /fractal:planning first."

Read in parallel:

1. plan.md — especially ## Execution DAG
2. predicate.md — the falsifiable condition for this node (the product reference)
3. prd.md — acceptance criteria (leaf nodes only; provides concrete validation targets)
4. .claude/project.md — build/test commands, hot files

Load project context

Scan the .fractal/ tree to understand what has already been built. This provides the agent with awareness of sibling nodes, previous deliveries, and accumulated project state.