architect-propose-plan

Creates standardized technical design proposals with URD traceability and review workflows.

1|Updated Mar 10, 2026

Search Tags:#workflow #design #planning #architecture #engineering #aura-protocol

Ready to run

npx skills add https://github.com/dayvidpham/pasture --skill architect-propose-plan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of consistency in technical planning by enforcing a structured, traceable, and review-ready format for engineering proposals.

Core Features & Use Cases

Structured Planning: Enforces a standardized template including problem axes, engineering tradeoffs, and public interfaces.
Traceability: Links proposals directly to URD requirements and research findings to ensure design decisions are grounded in context.
Lifecycle Management: Integrates with the Aura Protocol workflow to manage the review, ratification, and revision history of technical plans.

Quick Start

Execute the architect propose plan command to generate a new PROPOSAL-N task with the required design template and validation checklist.

Frequently Asked Questions about architect-propose-plan

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

FAQPage Schema

How do I standardize technical design proposals for engineering planning?▼

Standardizing technical design proposals requires enforcing a structured template that includes problem axes, engineering tradeoffs, and public interfaces. This approach ensures all engineering plans maintain consistency and are review-ready before implementation begins.

What is the best way to maintain traceability from requirements to engineering plans?▼

Maintaining traceability to requirements involves linking technical proposals directly to URD requirements and research findings. This structured documentation ensures every design decision remains grounded in the original project context and validates the engineering tradeoffs.

How do I structure an engineering plan that includes comprehensive tradeoffs and validation criteria?▼

Structuring an engineering plan with tradeoffs and validation criteria requires a standardized template covering problem axes and public interfaces. Enforcing this structured documentation ensures proposals include comprehensive engineering tradeoffs and defined validation criteria for formal review.

Can I manage the review and ratification lifecycle of technical plans within a structured workflow?▼

Managing the review and ratification lifecycle of technical plans is possible within the Aura Protocol workflow. This ecosystem facilitates the transition from requirements gathering to formal engineering plans by enforcing structured documentation and managing revision history.

Does the Aura Protocol support generating formal engineering plans from gathered requirements?▼

The Aura Protocol supports generating formal engineering plans from gathered requirements by facilitating the transition through structured documentation. It enforces traceability to URD requirements and ensures all proposals include comprehensive engineering tradeoffs and validation criteria.