spinoff

Forking a mid-session workstream requires generating a PM-authorized spinoff handoff that separates the newly surfaced topic into a pickup-ready task file with structured frontmatter, references, and acceptance criteria to avoid context switching.

PM-authorized spinoff creation is a gating mechanism that ensures an execution manager never splits an in-progress workstream without explicit product manager authorization for that specific topic, preventing unauthorized scope changes during active sessions.

Create a handoff document by running the spinoff command with a required slug-based filename and a one-line title, which generates a structured file containing frontmatter, specifications, acceptance criteria, and anti-scope boundaries for the picking-up EM.

Split a topic from an active session when a newly surfaced workstream is promising but separate from the current plan, and derailing the session to address it would cause context switching and scope drift.

Yes, optional chain discovery pulls related completion records for the same chain slug via bin/query-records to anchor the picking-up EM in existing workstream history.

The spinoff process enforces PM-authorization gating, meaning an EM cannot initiate a mid-session workstream split without specific PM authorization for that exact topic, preventing uncontrolled scope expansion.