architectural-proposals

Standardize technical architectural proposals with risk assessment and sign-off requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of alignment and technical debt caused by implementing features without a clear, documented architectural foundation.

Core Features & Use Cases

  • Structured Proposal Generation: Enforces a rigorous format for problem statements, technical solutions, and risk analysis.
  • Wave Restructuring: Provides a pattern for cascading impacts when architectural shifts change project milestones.
  • Decision Framing: Standardizes how technical trade-offs are presented to stakeholders for sign-off.
  • Use Case: When a major shift in the tech stack is required, use this Skill to draft a proposal that identifies risks, defines the new wave structure, and secures team consensus before writing a single line of code.

Quick Start

Use the architectural-proposals skill to draft a new proposal for the proposed database migration based on the current module map.

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 design proposal for a major tech stack migration?▼

Structure your technical design proposal by documenting the problem statement, proposed solution, impact analysis, and risk assessment. This ensures team alignment and explicit stakeholder sign-off before implementation begins.

What is architectural proposal documentation used for in software engineering?▼

Architectural proposal documentation standardizes how technical trade-offs, scope definitions, and risk mitigations are presented to stakeholders. It prevents technical debt by ensuring team alignment before implementation begins.

How do I document cascading impacts when architectural shifts change project milestones?▼

Document cascading impacts by applying wave restructuring patterns to map how architectural shifts alter project milestones. This captures downstream effects within the technical proposal for stakeholder review.

Do I need explicit sign-off requirements for an architecture proposal?▼

Yes, explicit sign-off requirements are mandatory. The architecture proposal enforces a structured format that standardizes technical trade-offs and risk assessment to secure formal stakeholder consensus before development.

What is the best way to frame technical trade-offs for stakeholders during database migration?▼

The best way to frame technical trade-offs is through standardized decision framing within the architectural proposal. This outlines problem statements, impact analysis, and risks to guide stakeholders toward informed sign-off.