architect

Coordinate end-to-end epoch planning specification and handoff workflows.

2|Updated Feb 7, 2026

Search Tags:#planning #specification #handoff #proposal #architect #urd

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architect coordinates end-to-end specification and handoff workflows for epoch planning, producing structured proposals and managing reviews.

Core Features & Use Cases

Owns Phases p1-p7 of the epoch planning lifecycle, including URD creation, PROPOSAL-N drafting, reviewer coordination, UAT, ratification, and handoff to a supervisor.
Spawns axis-specific reviewers (A, B, C) and ensures governance through a standard Beads-based workflow; integrates with /aura:* skills for role loading.
Maintains traceable provenance with clear references, status transitions, and handoff artifacts stored in .git/.aura/handoff.

Quick Start

Load the Architect role and start the PROPOSAL-N workflow by invoking /aura:architect with your initial user request.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I coordinate end-to-end epoch planning and proposal drafting?▼

Epoch planning workflows coordinate specification creation by owning phases p1 through p7, drafting PROPOSAL-N tasks, and managing reviewer coordination. This ensures structured proposal generation with traceable provenance for complex, multi-phase initiatives.

What is a URD and when do I need one for specification writing?▼

A URD is a user requirements document created during the initial phases of epoch planning for complex, multi-phase initiatives. It serves as the foundational specification artifact before drafting PROPOSAL-N tasks and coordinating axis-specific reviewer feedback.

How do I manage phase governance and reviewer coordination for specifications?▼

Phase governance and reviewer coordination are managed by spawning axis-specific reviewers A, B, and C within a standard Beads-based workflow. Role loading integrates with aura skills to evaluate PROPOSAL-N drafts before UAT and ratification.

Does this specification writer support BDD-style acceptance criteria and traceable provenance?▼

Yes, this specification workflow supports BDD-style acceptance criteria and maintains traceable provenance throughout the lifecycle. Clear references, status transitions, and handoff artifacts are generated and stored in the git aura handoff directory.

What are the limitations of using a structured proposal workflow for software planning?▼

Structured proposal workflows require significant overhead and are not suited for simple, single-phase tasks. This epoch planning approach is designed exclusively for complex, multi-phase initiatives requiring full phase governance, UAT, and role-based delegation.