subagent-mission-brief

Write a mission brief that names the Work Block and lifecycle stage, defines the review scope and required inputs, sets a read-only permission boundary, and specifies the expected response format. This keeps the reviewer focused and its output usable.

A brief includes four parts: identity and outcome (objective and expected handoff), scope and authority (in/out scope and required inputs), permission boundary (approved write-set or none), and evidence with hard stops (required checks and response format).

Skip delegation for trivial local tasks, one-line checks, simple status commands, and discussion-only turns. Delegation adds overhead that only pays off for non-trivial work like broad reviews, large file inspection, or scoped implementation.

Define an approved write-set in the permission boundary section of the brief, naming exactly which files the subagent may modify and who owns writer responsibility. Anything outside that set is out of bounds.

This copy is adapted for OpenCode with OpenCode-compatible tool references, but it is derived from a framework skill whose original remains authoritative. The brief structure itself is runtime-neutral.