architectural-proposals

Draft architectural proposals documenting problem statements, architecture, decisions, and risks.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill architectural-proposals-plagueho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architectural-proposals
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/architectural-proposals
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill architectural-proposals-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often delayed or misaligned, causing rework and scope creep. This Skill provides a structured approach to draft proposals that align stakeholders before coding begins.

Core Features & Use Cases

  • Structured proposal templates covering problem statements, proposed architecture, scope, and risks.
  • Decision framing, risk documentation, and wave-impact considerations to guide multi-team initiatives.
  • Reusable patterns that reduce rework and improve alignment across products and engineering teams.

Quick Start

Draft a proposal starter by outlining the problem and the proposed architecture in a new docs/proposals/ directory.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema
How do I document an architectural proposal for a cross-team initiative?▼

An architectural proposal documents the problem statement, proposed architecture, changes, decisions, risks, and scope. This structured approach aligns stakeholders on cross-team initiatives before any code is written.

What is the best way to align stakeholders before starting development on a product-direction shift?▼

The best way to align stakeholders on a product-direction shift is drafting a structured architectural proposal. It frames decisions, documents risks, and considers wave-impacts to guide multi-team initiatives before development begins.

Can I use structured proposal templates for multi-wave initiatives where requirements evolve?▼

Yes, structured proposal templates are specifically designed for multi-wave initiatives where requirements evolve. They document scope and wave-impact considerations to reduce rework and maintain alignment across teams.

Does this approach to architectural decisions help prevent scope creep and rework?▼

Yes, this approach prevents scope creep and rework by applying reusable patterns and structured templates. Aligning stakeholders through documented problem statements and scope boundaries delays or misaligns architectural decisions.

How do I start drafting an architectural proposal for a new project?▼

To start drafting an architectural proposal, outline the problem and the proposed architecture in a new docs/proposals/ directory. This initial starter frames the core decisions and risks for stakeholder review.