What problem does it solve? Changing a technology stack component (database, auth, hosting) without knowing which features break leads to unplanned migration work and lost architectural context. This Skill shows the current stack, analyzes the impact of proposed changes across all feature specs, and records decisions as ADRs. ## Core Features & Use Cases - Stack Visibility: Displays the current stack table from .specs/stacks/_default.md along with all architecture decision records. - Impact Analysis: Scans every feature's spec, plan, and implementation files to rate change impact as High, Medium, or Low, with effort estimates and migration strategy (big-bang, phased, hybrid) plus rollback requirements. - ADR Management: Creates dated ADR files, updates the decisions table in .specs/README.md, refreshes the preflight manifest, and optionally spawns migration specs per affected feature. - Use Case: Before switching from Supabase to Firebase, run the change command to see that 4 features are affected, get a 9-12 day effort estimate, and generate an ADR documenting the decision and consequences. ## Quick Start Ask the AI to run /spec-stack change followed by a description like "switch database to Firebase" to get an impact analysis and a draft ADR.