architect-request-review

Spawn three specialized reviewers to evaluate architectural proposals.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dayvidpham/pasture --skill architect-request-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-request-review
Source: https://github.com/dayvidpham/pasture/tree/main/.opencode/skill/architect-request-review
Command: npx skills add https://github.com/dayvidpham/pasture --skill architect-request-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of inconsistent or incomplete architectural reviews by standardizing the process of spawning specialized reviewers to evaluate proposals across critical quality axes.

Core Features & Use Cases

  • Multi-Axis Review: Automatically triggers three distinct reviewers (Correctness, Test Quality, and Elegance) for any given proposal.
  • Standardized Workflow: Enforces a consistent naming convention and consensus-based voting system (ACCEPT/REVISE) for all architectural proposals.
  • Use Case: When a new system design proposal is ready, use this Skill to spawn the three required reviewers, ensuring the proposal is vetted for technical correctness, testability, and architectural elegance before approval.

Quick Start

Use the architect-request-review skill to spawn three reviewers for the current proposal task by providing the task ID and the associated URD reference.

Frequently Asked Questions about architect-request-review

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

FAQPage Schema
How do I orchestrate a multi-axis architectural review for a system proposal?

Multi-axis architectural review is orchestrated by spawning three specialized reviewers to evaluate proposals based on correctness, test quality, and elegance. This coordinates the lifecycle of proposal review rounds within the Aura Protocol framework.

How do I track task IDs and manage comments for architectural proposal validation?

Tracking task IDs and managing review comments for proposal validation requires integration with the pasture CLI. This integration facilitates consensus tracking and manages the lifecycle of proposal review rounds.

What is the consensus voting system used for architectural code reviews?

The consensus voting system for architectural code reviews enforces a consistent naming convention and uses ACCEPT or REVISE votes. This standardized workflow ensures proposals are vetted across critical quality axes before approval.

Does the architectural review protocol require a specific task ID and URD reference to start?

Starting the architectural review protocol requires providing the current proposal task ID and the associated URD reference. These inputs spawn the three required reviewers to evaluate the proposal.

When do I need to spawn specialized reviewers for an architectural proposal?

Spawning specialized reviewers is needed when a new system design proposal is ready for vetting. This ensures the proposal is checked for technical correctness, testability, and architectural elegance before final approval.

Why does an architectural review workflow spawn separate reviewers for correctness, testability, and elegance?

Separate reviewers for correctness, testability, and elegance solve the challenge of inconsistent or incomplete architectural reviews. Standardizing the process across critical quality axes ensures comprehensive proposal validation.