bip.epic.handoff

Automating worker handoff requires spawning a follow-up issue and updating the EPIC dashboard to transition ongoing work to a new slot. This workflow coordinates clones or worktrees, queuing the next work item without manual orchestration when a clear next direction is decided.

Spawning a follow-up issue and updating an EPIC dashboard involves selecting or creating a slot from configuration while reconciling conflicts. The handoff action is invoked with the current issue number to determine the next direction and queue subsequent work automatically.

The automated handoff workflow supports both clone and worktree operation modes to keep transitions seamless across repository states. It coordinates ongoing work from a finishing worker to a new slot by updating the EPIC body and spawning follow-up issues.

You need to create a follow-up issue during a slot handoff when a worker completes an issue and next steps are unclear. The system determines a next direction, spawns follow-up work, and updates the EPIC body to ensure continuity and clarity of subsequent tasks.

You can select or create a new slot from configuration during an epic handoff while the system reconciles conflicts. This satisfies functional requirements for invoking the handoff, determining a next direction, and updating the EPIC body across collaborative software development workflows.

Automating epic handoffs is limited to collaborative software development workflows where issues, EPICs, and slots must be coordinated across clones or worktrees. It requires a current issue number to invoke the handoff action and relies on configuration to select or create the next slot.