What problem does it solve? When a master session fans an epic out into parallel batches, each receiving session needs a strict protocol for verifying its order, reporting scope before building, routing reserved decisions back to the master, and returning results that survive restarts. This Skill governs that engagement so parallel wave work stays coordinated instead of drifting. ## Core Features & Use Cases - Order verification and scope reporting: Reads the full batch (order, ledger, forge issues, code) before building and reports the actual scope found to the master before the first write. - Reserved-fork routing: Sends forks the order marks "agree with the master" to the master with analysis and recommendations, while deciding everything else autonomously. - Durable return protocol: Posts the full batch report to the tracker coordinate the order names, keeps the session engaged until the master accepts, and handles master-silent versus master-unreachable states. - Use Case: A session started from a wave chip uses this Skill to verify its worktree, read its batch's issues, build through the named workflow (usually implementation-workflow), report milestone statuses, and deliver a return the master can accept. ## Quick Start Invoke this skill in a session that received a batch order from a master session to verify the order, build the batch, and coordinate the return until acceptance.
