Implement with Subagents

Orchestrate approved backlog work while owning authority, order, verification, recovery, and acceptance. Give each work item a fresh subagent, but allow only one mutating agent at a time on the sole acceptance branch.

Under $to-product, its autonomous contract supplies owner approvals and blocker policy. Pass that contract and any run-transcript path through every brief.

Use $parallel-execution only for qualifying read-only questions or side-effect-free checks. Never run implementation workers concurrently.

Inputs

Require one explicit authorized scope: an active EPIC-NNN/path (authorizing all approved children and Epic closure) or a non-empty set of WORK-NNN IDs/paths. An unambiguous scope already established by the conversation counts; otherwise list candidates and ask — never infer a set from similar titles, changed paths, or rank adjacency. A set never authorizes siblings, parents, outside dependencies, or Epic closure; an Epic supplies coordination context but never expands a child's approved outcome.

Optional model and reasoning effort settings select the implementation tier. Keep $parallel-execution's read-only routing unless the user requires one uniform setting. If an interface cannot apply a setting, report that once and use its default.

Preflight

Before spawning or mutating backlog: