architectural-proposals

Name: architectural-proposals
Availability: InStock
Author: Sytone

Generate architectural proposals with problem statements, changes, risks, and decisions.

2|3|Updated Apr 1, 2026

Search Tags:#architecture #documentation #risk-management #team-alignment #decision-framing #architectural-proposals

Ready to run

npx skills add https://github.com/sytone/botnexus --skill architectural-proposals-sytone

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposals create alignment before code is written. Cheaper to change a doc than refactor code. Use this pattern when:

Architecture shifts invalidate existing assumptions
Product direction changes require new foundation
Multiple waves/milestones will be affected by a decision
External dependencies (Copilot CLI, SDK APIs) change

Core Features & Use Cases

Wave Restructuring Pattern: If a proposal changes foundations, clearly reframe waves and update dependencies to preserve parallel work where possible.
Decision Framing: Present a recommendation with alternatives, rationale, and required sign-offs to accelerate alignment.
Risk Documentation: Capture risk statements with likelihood, impact, and concrete mitigation steps to reduce uncertainties.
Examples & Anti-Patterns: Document common mistakes and best practices to guide consistent proposals.

Quick Start

Create a new proposal in docs/proposals/ following the required sections and include evidence, decisions, and risks.

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 architectural proposal that aligns teams before coding?▼

An architectural proposal aligns teams by documenting problem statements, proposed architecture, changes, risks, and decisions with explicit trade-offs and sign-offs. Creating this documentation before coding makes it cheaper to change a doc than refactor code.

When do I need to create an architecture proposal instead of just writing code?▼

You need an architecture proposal when architecture shifts invalidate existing assumptions, product direction changes require new foundations, multiple waves are affected, or external dependencies change. Early alignment prevents costly refactoring across affected milestones.

How do I document risks and trade-offs in software architecture documentation?▼

Document risks in architecture proposals by capturing risk statements with likelihood, impact, and concrete mitigation steps to reduce uncertainties. Frame decisions by presenting recommendations alongside alternatives, rationale, and required sign-offs to accelerate team alignment.

What is the best way to restructure development waves during major architecture shifts?▼

Use a wave restructuring pattern that clearly reframes waves and updates dependencies to preserve parallel work where possible. Document this in your proposal to maintain alignment across affected teams and milestones.

How do I accelerate team sign-offs on proposed architecture changes?▼

Accelerate team sign-offs on architecture changes by using explicit decision framing that presents a recommendation with alternatives, rationale, and required sign-offs. Including evidence, risks with mitigations, and examples of common mistakes guides consistent proposals and faster agreement.