Architect: Handoff to Supervisor

Create a HANDOFF document linking ratified proposals to Supervisor tasks.

2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/dayvidpham/aura-plugins --skill architect-handoff-to-supervisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architect: Handoff to Supervisor
Source: https://github.com/dayvidpham/aura-plugins/tree/main/skills/architect-handoff
Command: npx skills add https://github.com/dayvidpham/aura-plugins --skill architect-handoff-to-supervisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate handoffs of ratified proposals from Architects to Supervisors within the Beads-enabled workflow, ensuring linkage to the URD, RATIFIED PROPOSAL, and a HANDOFF document.

Core Features & Use Cases

  • Create and manage a HANDOFF document at .git/.aura/handoff/{request-id}/architect-to-supervisor.md.
  • Spawn and monitor a Supervisor Beads task that loads role instructions via Skill(/aura:supervisor) and orchestrates vertical-slice work.
  • Enforce workflow constraints, ensure leaf tasks are created for each vertical slice, and maintain traceability through references.
  • Use Case: When a ratified PROPOSAL-N exists, hand it off to a supervisor for implementation with linked URD/Proposal, and track progress via beads.

Quick Start

Load the Architect handoff workflow by triggering the supervisor role via Skill(/aura:supervisor) and begin handing off the ratified proposal to the supervisor.

Frequently Asked Questions about Architect: Handoff to Supervisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off a ratified proposal to a supervisor for implementation?

A proposal handoff links the ratified proposal and URD to a HANDOFF document, then spawns a Supervisor task that loads role instructions to orchestrate vertical-slice implementation work.

What is a Beads-enabled workflow for architect-to-supervisor handoffs?

A Beads-enabled workflow coordinates handoffs by spawning and monitoring a Supervisor task that orchestrates vertical-slice work, maintaining traceability through references to the URD and ratified proposal.

Do I need to load the Supervisor role before starting the handoff process?

Yes, the workflow enforces loading the Supervisor role via Skill(/aura:supervisor) at startup before proceeding, ensuring the supervisor has the correct instructions to manage implementation tasks.

How do I create a HANDOFF document for a ratified proposal?

The workflow creates a HANDOFF document at .git/.aura/handoff/{request-id}/architect-to-supervisor.md, linking the ratified proposal and URD to preserve references for traceability during implementation.

How are leaf tasks defined when handing off a ratified proposal?

Leaf tasks are defined for each vertical slice during the handoff process, where the Supervisor role orchestrates these slices to break down implementation work into manageable, tracked components.