How this skill is triggered — by the user, by Claude, or both
Slash command
/aura:architect-request-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Send PROPOSAL-N task to reviewers for feedback.
Send PROPOSAL-N task to reviewers for feedback.
-> Full workflow in PROCESS.md
Plan draft complete, ready for review.
Given plan ready when requesting review then spawn 3 axis-specific reviewers (A=Correctness, B=Test quality, C=Elegance) should never spawn reviewers without axis assignment
Given reviewers when assigning then provide Beads task ID and context should never expect reviewers to search
Reviews are named PROPOSAL-N-REVIEW-{axis}-{round} where:
| Axis | Focus | Key Questions |
|---|---|---|
| A | Correctness (spirit and technicality) | Does it faithfully serve the user? Are technical decisions consistent with rationale? |
| B | Test quality | Integration over unit? SUT not mocked? Shared fixtures? Assert outcomes? |
| C | Elegance and complexity matching | Right API? Not over/under-engineered? Complexity proportional to problem? |
Task(description: "Reviewer A: correctness", prompt: "Review PROPOSAL-1 task <task-id>. URD: <urd-id> (read for requirements context). You are Reviewer A (Correctness). Focus: Does it faithfully serve the user? Are technical decisions consistent with rationale? Create review task titled PROPOSAL-1-REVIEW-A-1...", subagent_type: "reviewer")
Task(description: "Reviewer B: test quality", prompt: "Review PROPOSAL-1 task <task-id>. URD: <urd-id> (read for requirements context). You are Reviewer B (Test quality). Focus: Integration over unit? SUT not mocked? Shared fixtures? Assert outcomes? Create review task titled PROPOSAL-1-REVIEW-B-1...", subagent_type: "reviewer")
Task(description: "Reviewer C: elegance", prompt: "Review PROPOSAL-1 task <task-id>. URD: <urd-id> (read for requirements context). You are Reviewer C (Elegance). Focus: Right API? Not over/under-engineered? Complexity proportional to problem? Create review task titled PROPOSAL-1-REVIEW-C-1...", subagent_type: "reviewer")
All 3 reviewers must vote ACCEPT. Max revision rounds until consensus.
bd show <proposal-id>
bd comments <proposal-id>
# Add comment to notify that review is ready
bd comments add <proposal-id> "Review requested — 3 reviewers spawned"
# Check for review votes
bd comments <proposal-id>
For FOLLOWUP_PROPOSAL-N reviews, use the same procedure:
FOLLOWUP_PROPOSAL-N-REVIEW-{axis}-{round}Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub dayvidpham/aura-plugins --plugin aura