architectural-proposals

Document architectural decisions with problem statements, risks, and ownership.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create thorough architectural proposals to align stakeholders and reduce rework before coding begins.

Core Features & Use Cases

  • Proposal Structure: documents include Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions, and Risks.
  • Wave Restructuring Pattern: handles shifts in the wave plan by reclassifying foundation work and cascading downstream impacts.
  • Decision Framing & Risk Documentation: explicit decisions, alternatives, rationale, and risk mitigations to improve traceability.
  • Use Cases: ideal for product direction changes, architecture reviews, and cross-team initiatives where multiple teams and waves are affected.
  • Example: before a major refactor, draft a proposal outlining the problem, the new architecture, impacts, and who must sign off.

Quick Start

Draft an architectural proposal that identifies the problem, selects a target architecture, and documents risks before starting implementation.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema
How do I document architectural decisions to align stakeholders before implementation?

Document architectural decisions by drafting proposals that outline the problem statement, proposed architecture, key decisions, risks, and explicit ownership to align stakeholders before implementation.

What is the best way to structure an architectural proposal for a product direction change?

The best structure for an architectural proposal includes a Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions, and Risks to frame cross-team decisions effectively.

How do I handle wave plan restructuring when foundation work shifts in an architecture review?

Handle wave plan restructuring by reclassifying foundation work and cascading downstream impacts within your architectural proposal to ensure cross-team alignment and traceability.

When do I need risk documentation and decision framing in architectural proposals?

You need risk documentation and decision framing in architectural proposals when multiple teams and waves are affected, requiring explicit alternatives, rationale, and risk mitigations to improve traceability.

Can I use architectural proposals for cross-team initiatives where multiple teams are affected?

Yes, architectural proposals are ideal for cross-team initiatives where multiple teams and waves are affected, applying structured patterns and explicit ownership to align stakeholders before implementation.