architecture-impactlisted

# Architecture Impact Analysis Analyze a PR's architectural impact. Produces a decision-maker-friendly document with visual before/after diagrams, business impact framing, and honest risk assessment. ## Audience and Principles The output targets **decision makers**: engineering leads, PMs, and stakeholders. **Core principles:** - **Outcomes over implementation.** Lead with what changes for users, teams, and the roadmap, not what was refactored internally. - **"So what?" test.** Every section must answer: why should a PM care about this? - **Progressive disclosure.** TL;DR first. Technical details exist for those who want them, but aren't required to understand the impact. - **Newspaper test.** If a PM read only the title, would they understand why it matters? "Enable independent deployments per framework" passes. "Extract fetch handler into core module" fails. - **One diagram = one question.** Write the question as the diagram title. If it answers multiple questions, split it. - **Honest tradeoffs.** PMs respect acknowledged risks far more than false reassurance. Always present what was rejected and why. ## Input This skill accepts PRs only. 1. Matches GitHub URL or `#\d+` pattern -> **PR** 2. No argument -> ask: "Which PR should I analyze? Provide a PR URL or number." 3. Anything else -> "This skill analyzes PRs only. Provide a PR URL or number." ## Process Flow ```dot digraph architecture_impact { rankdir=TB; "Resolve PR" [shape=box]; "Phase 1: Analyze