architectural-proposals

Draft structured architectural proposals with problem statements, decisions, and risks.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill architectural-proposals-quaid-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-proposals
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/architectural-proposals
Command: npx skills add https://github.com/quaid-app/quaid --skill architectural-proposals-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposals help teams reach alignment on architectural direction before coding, reducing miscommunication and costly rework.

Core Features & Use Cases

  • Proposal Structure: Enforces a consistent layout (Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions, Risks, Scope).
  • Decision Framing & Risk: Captures alternatives, rationale, and mitigations to guide choices.
  • Team Alignment: Clarifies scope, dependencies, and impact across waves and milestones.

Quick Start

Draft your first architecture proposal in docs/proposals/ with a clear problem statement and recommended decisions.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema
How do I document architecture proposals to align stakeholders before coding begins?

Architecture proposals align stakeholders by enforcing a structured format with problem statements, proposed architecture, key decisions, risks, scope, and impact on project waves. This documentation reduces miscommunication and costly rework across product, design, and engineering teams before development starts.

What should be included in an architecture proposal for a major system shift?

An architecture proposal for major shifts should include a problem statement, proposed architecture, what changes, what stays the same, key decisions, risks, and scope. Capturing alternatives, rationale, and mitigations guides choices and clarifies impact across waves and milestones.

How do I frame risks and decisions in technical scoping documentation?

Frame risks and decisions in scoping documentation by capturing alternatives, rationale, and mitigations. The proposal structure enforces dedicated sections for key decisions and risks, guiding choices and clarifying dependencies across product, design, and engineering teams.

Can I use architecture proposals for cross-team milestone planning?

Yes, architecture proposals support cross-team milestone planning by clarifying scope, dependencies, and impact across project waves. The structured format extends to major architecture shifts and cross-team decisions, aligning product, design, and engineering teams before coding begins.

When do I need a formal architecture proposal instead of just starting development?

You need a formal architecture proposal when facing major architecture shifts, cross-team decisions, or milestone planning. Proposals help teams reach alignment on architectural direction before coding, reducing miscommunication and costly rework across product, design, and engineering.