architectural-proposals

Create structured architectural proposals with problem statements and decision logs.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill architectural-proposals-waynewalterberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-proposals
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/architectural-proposals
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill architectural-proposals-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align architectural decisions early to prevent costly rework and miscommunication as code is written, ensuring all stakeholders share a common blueprint.

Core Features & Use Cases

  • Structured Proposal Template: Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions, and Risks documented in a single document.
  • Decision Framing and Risk Documentation: Explicit choices with rationales and mitigations to accelerate sign-off and reduce scope creep.
  • Wave-aware Planning: Documents how decisions impact current and downstream waves, milestones, and dependencies; supports parallel work where possible.

Quick Start

Start by gathering the user directive and the current architecture references, then create a structured proposal in docs/proposals/ with the required sections.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema
How do I write an architecture proposal that aligns stakeholders before coding starts?

To write an architecture proposal that aligns stakeholders, document the problem statement, proposed architecture, key decisions, and risks in a single structured document to ensure shared understanding before code is written.

What should be included in an architectural decision document to prevent rework?

An architectural decision document should include a problem statement, proposed architecture, what changes, what stays the same, key decisions, and a decision log to mitigate scope creep and prevent costly rework.

When do I need to create a formal architecture proposal for software changes?

You need to create a formal architecture proposal when architecture shifts occur, product direction changes, or multiple development waves are affected, ensuring downstream dependencies and milestones are documented.

How do I document architectural risks and decisions for downstream development waves?

Document architectural risks and decisions by framing explicit choices with rationales and mitigations, and mapping how these decisions impact current and downstream waves, milestones, and dependencies.

Does generating an architecture proposal require existing architecture references?

Generating an architecture proposal requires gathering the user directive and current architecture references as input to create a structured proposal document in the docs/proposals/ directory with the required sections.