architectural-proposals

Standardize technical architectural proposals with problem statements and risk analysis.

1|Updated Dec 23, 2025

Search Tags:#architecture #documentation #alignment #risk-assessment #proposal #technical-design

Ready to run

npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill architectural-proposals-jonnymuir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architectural-proposals
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/architectural-proposals
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill architectural-proposals-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of technical alignment and documentation debt by providing a rigorous framework for proposing architectural changes before implementation begins.

Core Features & Use Cases

Structured Proposal Templates: Enforces a standardized format including problem statements, technical specifics, and risk analysis.
Decision Framing: Facilitates clear, evidence-based decision-making with explicit sign-off requirements.
Wave Restructuring: Provides patterns for managing complex project timelines when foundational architecture shifts.
Use Case: Use this when proposing a major refactor or a new system component to ensure all stakeholders understand the impact, risks, and technical rationale before writing code.

Quick Start

Use the architectural-proposals skill to generate a new proposal document in the docs/proposals directory based on the current problem statement.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema

How do I write a technical architectural proposal for a major system refactor?▼

Create an architectural proposal by standardizing documentation with problem statements, impact analysis, and explicit decision framing to drive technical alignment and mitigate risks before implementation begins.

What is the best way to document technical alignment for complex system design changes?▼

Document technical alignment by applying a rigorous proposal framework featuring standardized templates, evidence-based decision framing, and explicit sign-off requirements to mitigate risks before implementation.

When do I need an architectural proposal for product direction shifts?▼

You need an architectural proposal when managing complex system design changes, product direction shifts, or foundational infrastructure updates to ensure stakeholders understand impact, risks, and technical rationale before writing code.

Can I use structured proposal templates to manage wave restructuring for project timelines?▼

Yes, structured proposal templates provide patterns for managing complex project timelines and wave restructuring when foundational architecture shifts, ensuring explicit sign-off requirements and risk analysis are documented.

How does decision framing work in technical design documentation?▼

Decision framing in technical design documentation facilitates clear, evidence-based decision-making by enforcing explicit sign-off requirements and structured risk analysis within the architectural proposal before development proceeds.

Why does documentation debt occur without structured architectural proposals?▼

Documentation debt occurs without structured architectural proposals because there is no rigorous framework enforcing problem statements, impact analysis, and risk mitigation, leading to a lack of technical alignment before implementation begins.