architectural-proposals

Analyze codebases and create structured architectural proposals with risk mitigations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that architectural proposals drive alignment before coding, reducing rework and facilitating effective decision-making.

Core Features & Use Cases

  • Problem Analysis: Analyze codebases and documentation for inconsistencies or gaps.
  • Proposition Creation: Create proposals with structured format to guide technical direction.
  • Risk Mitigation: Assess and document potential risks and their mitigations.
  • Use Case: A project manager creates a proposal for a new feature to replace an existing, broken component. This proposal outlines the new architecture, expected impacts, and recommended steps.

Quick Start

Start by analyzing the existing codebase and documentation. Write a comprehensive proposal in the 'docs/proposals/' directory.

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 my team before coding starts?

Writing an architectural proposal for alignment involves analyzing your existing codebase and documentation for gaps, then documenting decisions, expected impacts, and mitigation strategies in a structured format within your docs directory.

What is the best way to document technical risks and mitigations for a new project architecture?

Documenting technical risks and mitigations is achieved by assessing potential issues during the architectural proposal creation process, recording both the risks and their mitigation strategies to ensure clear project direction and effective decision-making.

Can I analyze an existing codebase to find architectural gaps before proposing a new feature?

Analyzing an existing codebase for architectural gaps is a supported feature that allows you to identify inconsistencies or missing documentation, providing the foundational context needed to guide technical direction and create effective replacement proposals.

When do I need a structured architectural proposal for project management?

A structured architectural proposal is needed when you must align project vision and mitigate future risks before coding begins, ensuring that technical direction, impact, and mitigation strategies are clearly documented to prevent development rework.

Does this approach work for replacing broken components with a new architecture?

This approach works for replacing broken components by guiding the creation of a technical proposal that outlines the new architecture, documents expected impacts, and provides recommended steps to effectively manage the transition and mitigate risks.