architect-handoff

Transition architectural plans into implementation tasks by creating a structured handoff document within a Beads task and spawning an Opus supervisor teammate. This standardizes the handoff process, ensuring all context, requirements, and acceptance criteria are preserved for the supervisor.

Automate supervisor agent initialization by using the architect-handoff protocol to spawn an Opus supervisor teammate. It provides the necessary instructions to initiate the implementation phase and begin decomposing the work into vertical slices.

The Aura Protocol workflow handles task decomposition and monitoring by spawning supervisor agents that break architectural proposals into vertical slices. It uses Beads task tracking to ensure consistent monitoring across all development phases.

Yes, you can use Beads task tracking to preserve acceptance criteria during a handoff. The skill creates a structured handoff document within the Beads task, ensuring all context and requirements are maintained for the supervisor.

Yes, a ratified architectural proposal is required before spawning a supervisor teammate. The skill operates within the Aura Protocol workflow to transition these ratified proposals into actionable implementation plans.

Structured handoff documentation for supervisor orchestration solves the communication gap between architectural planning and technical implementation. It ensures the Opus supervisor correctly loads its role instructions and autonomously begins task decomposition.