supervisor

Coordinate vertical slice development with ephemeral reviewers and Beads task tracking.

2|Updated Feb 7, 2026

Search Tags:#automation #workflow #beads #multi-agent #coordination #slices #ephemeral-reviewers

Ready to run

npx skills add https://github.com/dayvidpham/aura-plugins --skill supervisor-dayvidpham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supervisor
Source: https://github.com/dayvidpham/aura-plugins/tree/main/skills/supervisor
Command: npx skills add https://github.com/dayvidpham/aura-plugins --skill supervisor-dayvidpham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams coordinate parallel development efforts by dividing work into vertical slices, spawning workers, and coordinating reviews without direct implementation.

Core Features & Use Cases

Vertical slices: End-to-end ownership of a feature from types to wiring.
Ephemeral review: Spawn per-slice reviewers to validate work without standing teams.
Ride the Wave orchestration: Plan, build, and review cycles with strict limits and escalation.
Handoff-ready coordination: Create and manage handoffs between architect, supervisor, workers, and reviewers for traceability.
Beads-driven context: All tasks link through Beads for status, comments, and dependencies.

Quick Start

Invoke Skill(/aura:supervisor) to load role instructions, then read the RATIFIED_PLAN and URD to map the work and begin Phase 8 IMPL_PLAN.

Frequently Asked Questions about supervisor

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

FAQPage Schema

How do I coordinate parallel development tasks across multiple agents?▼

Orchestrate parallel development by dividing work into vertical slices, spawning ephemeral workers, and coordinating handoffs through Beads task coordination. This ensures predictable end-to-end software delivery without requiring standing review teams.

What is ephemeral review in multi-agent workflow coordination?▼

Ephemeral review spawns temporary per-slice subagents to validate specific work slices without maintaining standing teams. This enables constrained review cycles with strict limits and escalation protocols during end-to-end software delivery.

How do I start a workflow using vertical slices and Beads task coordination?▼

Start vertical slice workflows by loading role instructions, then reading the RATIFIED_PLAN and URD to map work. Begin Phase 8 IMPL_PLAN by modeling vertical slices and per-slice leaf tasks with explicit integration points for predictable delivery.

Can I use this multi-agent orchestration for large software delivery phases?▼

Yes, you can use this multi-agent orchestration for large software delivery phases, specifically Phase 7 through 12 of an epoch. It models vertical slices and per-slice leaf tasks with constrained review cycles, applying explicit integration points to ensure predictable delivery at scale.

When should I not use ephemeral reviewers for workflow automation?▼

Avoid using ephemeral reviewers when workflows require direct implementation or permanent standing teams. This orchestration approach coordinates handoffs and validates work without direct implementation, relying strictly on Beads-driven context for status, comments, and dependencies.