protocol

Document the Aura Protocol's 12-phase workflow, agent roles, and coding standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a canonical, machine-readable reference and a clear, human-friendly guide to the Aura Protocol's 12-phase workflow, agent roles, constraints, and coding standards.

Core Features & Use Cases

  • Canonical Reference for the 12-phase Beads workflow and role responsibilities.
  • Guidance for Onboarding new team members and maintaining protocol conformance across projects.
  • Governance & Handoff Support through standardized handoffs, reviews, and artifact templates used across the lifecycle.

Quick Start

Consult PROCESS.md and AGENTS.md to understand how to apply the Aura protocol in projects.

Frequently Asked Questions about protocol

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

FAQPage Schema
What is the Aura Protocol workflow and when do I need it?

The Aura Protocol workflow is a structured 12-phase lifecycle process for Beads-based orchestration. You need it when managing complex projects requiring standardized agent roles, cross-team handoffs, and strict protocol conformance checks across all phases.

How do I onboard new team members to the Aura Protocol 12-phase workflow?

To onboard new team members to the Aura Protocol, consult PROCESS.md and AGENTS.md. These canonical references provide the machine-readable workflow phases, agent role responsibilities, and coding standards needed for immediate protocol conformance.

How does Beads-based orchestration handle agent handoffs in the Aura Protocol?

Beads-based orchestration handles handoffs in the Aura Protocol through standardized review templates and artifact handoffs. This ensures governance support and consistent transitions across the 12-phase lifecycle by defining explicit agent roles and constraints.

Can I use the Aura Protocol for cross-team project governance and discovery?

Yes, you can use the Aura Protocol for cross-team project governance and discovery. It serves as a single source of truth, providing standardized artifact templates and coding standards that maintain protocol conformance and support consistent implementation across teams.

What's the best way to audit protocol conformance across the 12-phase workflow?

The best way to audit protocol conformance across the 12-phase workflow is using the canonical reference defined in PROCESS.md. It provides the machine-readable constraints, agent role responsibilities, and coding standards required to validate implementation and governance at any phase.

Do I need specific dependencies to implement the Aura Protocol workflow?

No specific external dependencies are required to implement the Aura Protocol workflow. The protocol operates as a self-contained governance reference using standardized templates and Beads-based orchestration rules to guide implementation and audits independently.