architectural-proposals

Generate structured architecture proposals with problem statements, decisions, and risk assessments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align teams and decisions by documenting a clear architectural proposal before coding begins, reducing rework and misalignment.

Core Features & Use Cases

  • Structured proposal blueprint with required sections: Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions, Risks and Mitigations, Scope.
  • Facilitates early stakeholder alignment, risk assessment, and architectural governance across projects.
  • Use Case: When starting a new system or major redesign, produce a proposal to guide design decisions and milestone planning.

Quick Start

Draft an architectural proposal that defines the problem, proposed solution, scope, decisions, and risks for your upcoming project.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema
What is an architecture proposal and why do I need one before coding begins?

An architecture proposal is a structured document that defines a problem statement, proposed solution, and key risks to align stakeholders before coding begins, reducing rework and misalignment across software projects.

How do I structure an architectural proposal for stakeholder alignment?

Structure an architectural proposal using required sections: Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions, Risks and Mitigations, and Scope to drive stakeholder alignment and decision-making.

What should I include in the risk assessment section of a software architecture proposal?

Include identified risks and their corresponding mitigations in the risk assessment section of an architecture proposal to facilitate early stakeholder alignment and architectural governance across the project.

Can I use an architecture proposal for a major system redesign and wave planning?

Yes, use an architecture proposal when starting a new system or major redesign to guide design decisions, define what changes versus what stays the same, and plan milestones for wave planning across software systems.

What is the best way to document architectural decisions for stakeholders?

The best way to document architectural decisions is a proposal-first approach specifying key decisions, proposed architecture, and scope to drive alignment and governance before development starts.

When should I not use an architecture proposal-first approach?

An architecture proposal-first approach is not suitable for minor changes that require no architectural decisions, risk assessment, or stakeholder alignment, as the documentation overhead outweighs the benefit of structured governance.