architectural-proposals

Document architectural proposals with defined sections, risks, and decisions.

413|64|Updated Feb 7, 2023
One-click install
npx skills add https://github.com/christianhelle/refitter --skill architectural-proposals-christianhelle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-proposals
Source: https://github.com/christianhelle/refitter/tree/main/.copilot/skills/architectural-proposals
Command: npx skills add https://github.com/christianhelle/refitter --skill architectural-proposals-christianhelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposals create alignment before code is written. They capture context, decisions, and risks so teams can move faster with fewer refactors later.

Core Features & Use Cases

  • Proposal Structure: Documents required sections (Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions Needed, Risks and Mitigations, Scope).
  • Tone & Guidance: Enforce evidence-based reasoning, explicit decisions, and risk analysis to keep proposals focused and testable.
  • Wave & Dependency Awareness: Provides guidance on how foundational changes cascade through project waves and team decisions.
  • Artifacts & Examples: Points to docs/proposals templates and decision artifacts to streamline work.
  • Use Scenarios: Ideal for architecture shifts, product-direction realignments, and multi-wave planning.

Quick Start

Draft a concise architectural proposal describing the problem, the proposed solution, and its impact before any implementation begins.

Frequently Asked Questions about architectural-proposals

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

FAQPage Schema
How do I document architectural decisions before starting development?

You need an architectural proposal to align teams before code is written by capturing context, decisions, and risks. It is applicable during major architectural shifts, product-direction realignments, and multi-wave design changes.

What sections should be included in an architectural proposal template?

An architectural proposal template should include Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions Needed, Risks and Mitigations, and Scope sections to keep documents focused and testable.

How do I frame risks and mitigations for a major product direction realignment?

To frame risks and mitigations for a product direction realignment, use structured architectural proposals to document explicit risk analysis alongside foundational changes. This tracks how architectural shifts cascade through project waves and team decisions.

When do I need to write an architectural proposal for multi-wave design changes?

You need an architectural proposal during major architectural shifts, product-direction realignments, and multi-wave design changes. It provides wave-impact guidance to align teams before code is written and reduce future refactors.

What is the best way to align architecture decisions across multiple project waves?

The best way to align architecture decisions across project waves is using structured proposals with wave-impact guidance. This enforces evidence-based reasoning and documents how foundational changes cascade through team decisions.