Architect: Handoff to Supervisor

Pass ratified PROPOSAL-N to supervisor for implementation.

When to Use

Plan ratified and user has approved proceeding with implementation.

Given/When/Then/Should

Given ratified PROPOSAL-N task when handing off then create handoff document and HANDOFF task should never hand off without linking to ratified proposal

Given handoff when spawning supervisor then use aura-parallel --role supervisor or aura-swarm start --epic <id> should never spawn supervisor as Task tool subagent

Given implementation planning when handing off then let supervisor create vertical slice tasks should never create implementation tasks as architect

Handoff Template

Storage: .git/.aura/handoff/{request-task-id}/architect-to-supervisor.md

markdown

# Handoff: Architect → Supervisor

## Supervisor Startup
1. Call `Skill(/aura:supervisor)` to load your role instructions
2. Create a standing explore team via TeamCreate before any codebase exploration
3. Read the RATIFIED PROPOSAL and URD with `bd show` commands below
4. Every vertical slice MUST have leaf tasks (L1: types, L2: tests, L3: impl)

## References
- REQUEST: <request-task-id>
- URD: <urd-task-id> (read with `bd show <urd-id>`)
- RATIFIED PROPOSAL: <ratified-proposal-id> (read with `bd show <proposal-id>`)

## Summary
<1-2 sentence summary of what needs to be implemented>

## Key Files
<list main files to be created/modified from the ratified plan>

## Validation Checklist
<validation checklist from the ratified proposal>

## BDD Acceptance Criteria
<Given/When/Then criteria from the ratified plan>

## Implementation Notes
<any special considerations, known risks, or constraints>

Steps

•

Create the handoff document:

bash

mkdir -p .git/.aura/handoff/<request-task-id>/
# Write architect-to-supervisor.md with the template above

•

Create HANDOFF Beads task:

bash

bd create --type=task --priority=2 \
  --title="HANDOFF: Architect → Supervisor for REQUEST" \
  --description="---
references:
  request: <request-task-id>
  urd: <urd-task-id>
  proposal: <ratified-proposal-id>
---
Handoff from architect to supervisor. See handoff document at
.git/.aura/handoff/<request-task-id>/architect-to-supervisor.md" \
  --add-label "aura:p7-plan:s7-handoff"

bd dep add <request-id> --blocked-by <handoff-id>

•

Launch supervisor:

bash

# Using aura-parallel (for long-running supervisor in tmux session)
aura-parallel --role supervisor -n 1 --prompt "..."

# Or using aura-swarm (for epic-based worktree workflow)
aura-swarm start --epic <id>

•

Monitor supervisor progress:

bash

# Check beads status
bd list --status=in_progress

# Or attach to supervisor session (if using aura-parallel)
tmux attach -t supervisor--1-<hex4>

Example Prompt

CRITICAL: The prompt MUST instruct the supervisor to invoke /aura:supervisor as its first action. Without this, the supervisor agent starts without its role instructions and skips leaf task creation, explore team setup, and other critical procedures.

code

Start by calling `Skill(/aura:supervisor)` to load your role instructions.

Implement the ratified plan for <feature name>.

## Context
- REQUEST: <request-task-id>
- URD: <urd-task-id> (read with `bd show <urd-id>` for user requirements)
- RATIFIED PROPOSAL: <ratified-proposal-id>
- HANDOFF: <handoff-task-id>
- Handoff document: .git/.aura/handoff/<request-task-id>/architect-to-supervisor.md

## Summary
<1-2 sentence summary of what needs to be implemented>

## Key Files
<list main files to be created/modified from the ratified plan>

## Acceptance Criteria
<Given/When/Then criteria from the ratified plan>

## Reminders
1. Call `Skill(/aura:supervisor)` FIRST — do not proceed without loading your role
2. Create a standing explore team via TeamCreate BEFORE doing any codebase exploration
3. Every vertical slice MUST have leaf tasks (L1: types, L2: tests, L3: impl) — a slice without leaf tasks is undecomposed
4. Read the ratified plan with `bd show <ratified-proposal-id>` and the URD with `bd show <urd-id>`

Pass the prompt to the script:

bash

aura-parallel --role supervisor -n 1 --prompt "$(cat <<'EOF'
Start by calling Skill(/aura:supervisor) to load your role instructions.

Implement the ratified plan for User Authentication.

## Context
- REQUEST: project-abc
- URD: project-xyz
- RATIFIED PROPOSAL: project-prop1
- Handoff document: .git/.aura/handoff/project-abc/architect-to-supervisor.md

## Summary
Add JWT-based authentication with login/logout endpoints and middleware.

## Key Files
- pkg/auth/jwt.go
- pkg/auth/middleware.go
- cmd/api/auth.go

## Acceptance Criteria
Given a valid JWT token when accessing protected routes then allow access
Given an expired token when accessing protected routes then return 401

## Reminders
1. Call Skill(/aura:supervisor) FIRST
2. Create standing explore team via TeamCreate before codebase exploration
3. Every slice MUST have leaf tasks (L1/L2/L3)
4. Read ratified plan: bd show project-prop1 and URD: bd show project-xyz
EOF
)"

Script Options

bash

aura-parallel --role supervisor -n 1 --prompt "..."             # Launch supervisor
aura-parallel --role supervisor -n 1 --prompt "..." --dry-run   # Preview without launching
aura-parallel --role supervisor -n 1 --prompt-file prompt.md    # Read prompt from file

IMPORTANT

•DO NOT spawn supervisor as a Task tool subagent - use aura-parallel or aura-swarm
•DO NOT create implementation tasks yourself - the supervisor creates vertical slice tasks
•DO NOT implement the plan yourself - your role is handoff and monitoring
•The supervisor reads the ratified plan and determines vertical slice structure
•Architect monitors for blockers or escalations

Follow-up Lifecycle (h1 Reuse)

This handoff (h1: Architect → Supervisor) also occurs after FOLLOWUP_PROPOSAL is ratified. In follow-up context:

•Storage: .git/.aura/handoff/{followup-epic-id}/architect-to-supervisor.md
•References: Include both original URD and FOLLOWUP_URD task IDs
•Context: Summary of FOLLOWUP_PROPOSAL ratification and outstanding leaf tasks from original review
•Next step: Supervisor creates FOLLOWUP_IMPL_PLAN and FOLLOWUP_SLICE-N tasks, adopting original IMPORTANT/MINOR leaf tasks as dual-parent children