architect-ratify

Validate reviewer consensus and update proposal metadata via the pasture CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the bottleneck of manual proposal ratification by enforcing strict consensus requirements and automating the transition of proposal states within the Aura Protocol.

Core Features & Use Cases

  • Consensus Enforcement: Ensures all three required reviewers have provided an ACCEPT vote before allowing ratification.
  • Lifecycle Management: Automatically marks superseded proposals with the appropriate labels and audit trail comments.
  • Use Case: When a technical plan reaches the final review stage, use this skill to verify reviewer sign-offs, label the proposal as ratified, and clean up outdated versions to maintain a clear audit trail.

Quick Start

Use the architect-ratify skill to verify that all three reviewers have accepted the proposal and to mark previous versions as superseded.

Frequently Asked Questions about architect-ratify

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

FAQPage Schema
How do I automate technical proposal ratification and enforce reviewer consensus?

Automating proposal ratification requires validating that all three designated reviewers provide an ACCEPT vote before transitioning the proposal state. The architect-ratify skill enforces this strict consensus requirement and applies the appropriate ratified labels to approved technical plans.

Do I need the pasture CLI to update proposal metadata and audit trail comments?

Yes, you need the pasture CLI installed to execute label updates and comment logging against the local task database. The ratification workflow relies on this CLI to ensure consistent state transitions and maintain audit trail integrity.

How does proposal lifecycle management handle superseded technical plans?

Proposal lifecycle management automatically marks superseded technical plans with the appropriate labels and audit trail comments. This ensures outdated versions are cleaned up during the ratification phase to maintain a clear and accurate audit trail.

What happens if not all three reviewers accept a technical proposal?

If not all three required reviewers provide an ACCEPT vote, the proposal ratification process blocks the state transition. Consensus enforcement ensures strict validation of reviewer sign-offs before any proposal is marked as ratified.

Can I use this workflow for proposal state transitions outside the Aura Protocol?

This workflow specifically applies to the Aura Protocol to ensure consistent state transitions and audit trail integrity. It is designed to validate reviewer consensus and manage proposal metadata within this specific technical framework.