Fourth Wall

Use this skill when the user requests multi-agent coordination or when disjoint ownership or task risk makes a bounded task tree useful. If neither condition applies, stay single-agent. When a tree exists, use this skill for routing, synchronization, review, recovery, or handoff. A depth-1 Terra/Sol Worker follows it before using its single bounded delegation allowance.

The skill solves one coordination problem: divide work without losing the full outcome, overlapping ownership, wasting root context on delegated loops, or accepting prose as proof. Complexity and horizon select a capability pair; a behavioral role selects the duty and task-name prefix. When the Skizzles profile is installed, generated capability-bearing agent_type values persist that pair through reactivation. The root owns the graph, integration, and final acceptance.

Applicability and authority

Apply delegation, independent review, runtime proof, and Git checkpoints only when the task type, user request, changed boundary, or risk makes them relevant. Report-only, documentation, and prompt work may stay single-agent and use focused text or configuration checks; this skill does not require unrelated runtime checks or a commit.

For requested local implementation, build, or fix work, the owner may inspect files, edit in-scope code, and run relevant non-destructive checks without an extra approval step. External, destructive, credentialed, production, or host-environment writes require explicit operator confirmation. An approval reviewer may inspect, route, and record a request, but cannot provide that confirmation. The root retains Git integration and history authority.

Audience and scope

• Operate within the current root task tree. Native task paths and messaging do not cross unrelated top-level Desktop tasks.
• Keep the root focused on the overall outcome, decisions, dispatch, integration acceptance, and evidence evaluation.
• Delegate complete ownership slices with a clear owner, boundary, implementation, validation, and evidence contract. Do not retain the expensive execution loop at the root merely because delegation is active.
• Stay single-agent when coordination overhead would exceed the value of delegation.
• Children are peers beneath the root. Non-Workers return further decomposition to the root. A depth-1 Terra/Sol Worker may dispatch one active bounded Worker only when it can transfer a small, disjoint, end-to-end ownership slice while continuing independent implementation.