architectural-proposals

Generate architectural proposals documenting problems, solutions, impact, decisions, and risks.

3.1k|475|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/bradygaster/squad --skill architectural-proposals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-proposals
Source: https://github.com/bradygaster/squad/tree/main/.squad/skills/architectural-proposals
Command: npx skills add https://github.com/bradygaster/squad --skill architectural-proposals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams create and align on architectural proposals before writing code, reducing costly rework and ensuring clear technical direction.

Core Features & Use Cases

  • Structured Proposal Creation: Guides users to write comprehensive proposals with problem statements, proposed solutions, impact analysis, and risk assessments.
  • Decision Framing: Provides a clear format for making and documenting key technical decisions.
  • Use Case: When a significant change in product direction requires a new foundational architecture, this Skill can be used to generate a formal proposal that outlines the necessary changes, their impact on existing work, and the decisions that need to be made.

Quick Start

Use the architectural-proposals skill to draft a proposal for a new feature, outlining the problem, proposed solution, and impact on current development waves.

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 for a product direction change?

Document the problem, proposed solution, impact analysis, and risk assessment to drive team alignment on technical direction before implementation begins.

What should be included in technical design proposals to ensure team alignment?

Technical design proposals should include structured problem statements, proposed solutions, impact analysis on current development waves, decision framing, and risk assessments to ensure comprehensive team alignment.

When do I need a formal architectural proposal before writing code?

You need a formal architectural proposal before writing code when facing architecture shifts, product direction changes, or external dependency updates to prevent costly rework and establish clear technical direction.

How do I document technical decisions and impact analysis for a new architecture?

Document technical decisions and impact analysis by framing the problem, outlining the proposed solution, and detailing the impact on existing development work and identified risks to formalize the architectural shift.

Does this approach work for managing external dependency updates?

Yes, generating a structured architectural proposal works for managing external dependency updates by providing a clear format for documenting the problem, solution, impact, and risks involved.