/wakeflow-target

name: wakeflow-target
description: Use when a target Claude Code window receives an exact Wakeflow v3 delivery, executes only its assigned TaskPackage, records a transport-bound TargetResult, or performs an authorized Controller return without taking controller authority.

Wakeflow Target

Use this skill only inside the target window named by the current delivery. Workspace and repository `CLAUDE.md` files remain hard boundaries. The prompt orients; the immutable TaskPackage owns complete task context; anchored requirement documents own background; listed Skills own execution procedure.

Prompt Shape

Target wakeups stay task-first and compact:

Continue current window task: <currentWindow> / <taskId>.

Current objective (the task package is authoritative):
- <one-line objective>

Completion focus (up to two; full criteria are in the task package):
- <bounded observable result>
- <optional second bounded observable result>

- Priority context: <highest-priority confirmed fact>
- Critical boundary [forbidden|outOfScope|inScope]: <highest-priority boundary>

Key acceptance anchors (full probes and expectations are in the task package):
- <anchor id>: <claim>

Read before execution, in order:
- Task package (complete task context): <absolute package path>
- Requirement background entry: <document#section>
- Workspace instructions (only when distinct from repository instructions): <workspace>/CLAUDE.md
- Repository instructions: <repository>/CLAUDE.md
- Current state root: <absolute state-root path>

Required execution Skills (execution-process authority):
- skills/wakeflow-target/SKILL.md
- <other package-selected Skill>

Identity (full boundaries are in the task package):
- Current responsibility window: <window>
- Only working repository: <absolute repository path>

Before coding: map every `acceptanceAnchors` entry to a RED test or probe; return
needs-review instead of inventing a requirement when an anchor cannot be tested.

Return requirement:
- Execute only this TaskPackage and record a TargetResult with reproducible,
  target-authored review inputs. It is never controller acceptance.
- Test execution contract: <dispatch packet path>#testContract.executionContract

Dispatch record (routing and trace only):
- taskId: <taskId>
- taskPackageId: <package>
- stateRoot: <path>
- stateRevision: <revision>
- dispatchGroup: <group>

The prompt may omit conditional lines. It does not repeat the complete requirement, boundary lists, probes, Test policy, commit policy, or result contract. Read the TaskPackage first and treat prompt routing fields only as freshness/navigation anchors.

Target Flow

1. Confirm identity and authority.

• Arrival proves only transport, not authorization beyond the exact

envelope/TaskPackage.

• Confirm the typed target window, task, demand, dispatch group, packet, and

current delivery lineage. A title, cwd, tmux pane, or prompt assertion is not identity.

• Read the listed workspace/repository `CLAUDE.md` files and declare the one

repository responsibility before changing anything. 2. Read the complete task.

• Read the exact TaskPackage, ordered requirement refs, and every listed

execution Skill.

• Follow the packet's ordered `taskBriefing.requiredSkills`. Non-Test packets

load `skills/wakeflow-target-craft/SKILL.md` and map each package anchor to a RED probe; Test packets load `skills/wakeflow-test/SKILL.md`.

• If the packet carries `testContract`, pass the Test Alignment Gate below first.

3. Execute within the one assigned repository.

• Do not claim another target, Test role, controller role, or repository.
• Claude subagents may gather bounded evidence, but this target owns the

result and boundary decisions.

• If another repository or a product decision is required, stop and return a

concrete blocker instead of widening scope. 4. Produce reviewable inputs.

• Name changed files, diffs/commits, commands and outcomes, logs, reports,

runtime observations, screenshots, and residual risks as applicable.

• Prose alone is not completion evidence.

5. Import the TargetResult.

• Call `wakeflow_record_target_result` with `operation: "import"`, the typed

`demandId`, and `request:{artifact,transition}`. The transition is exactly `{eventId,createdAt,reason,decisionSummary}`. Do not write a local result file, inject an expected state selector, or choose an envelope by mtime.

• The owner accepts only the strict current group → packet → target envelope

→ accepted/ambiguous run → settlement lineage. A first result for a new envelope is a new round, not a correction. Same-envelope correction must use the exact supersedes tuple selected by the owner.

• Report `outcome` as `completed`, `blocked`, or `needs-review` honestly,

with a non-empty summary, exact `repositoryChanges`, `evidenceLocators`, verification outcomes, risks, and `craftMapping`. 6. Perform a Controller return only when the strict current snapshot allows it.

• Call `wakeflow_review_pack operation=group` for this demand/group. It is a

read-only snapshot, not permission to inspect another group or decide acceptance.

• When the current return unit is eligible, call

`wakeflow_prepare_delivery operation=controller-preview`, inspect the exact result-set/review/binding digests, then call `controller-apply` with the confirmed plan. Immediately before the host effect call `controller-pre-send` and require its current redacted read model.

• Route the effect through the packaged v3 Claude host facade's exact

`controller-return` command. Its transport owner holds the stable-window operation mutex across validation, physical paste, and at most one bounded readback. Retired public-v2 `deliver`/registry commands are not aliases. If exact host execution or its receipt is unavailable, stop at pre-send and report the bloc