What problem does it solve? Specs and code drift apart over time, and months later nobody remembers why a feature was built the way it was. This Skill answers "how does X work?" by synthesizing information from spec files, implementation maps, changelogs, and architecture decision records without reading source code. ## Core Features & Use Cases - Living Documentation: Generates an 8-section structured explanation (what it does, who uses it, flows, data model, file locations, rationale, history) with embedded Mermaid diagrams. - Intent-Based Query Resolution: Classifies questions as how/why/what-changed/where and prioritizes the right sources (ADRs for why, changelog for history, implementation map for locations). - Natural Language Search: Accepts feature names or free-form questions, ranking the top 3 candidate features when multiple matches exist. - Use Case: A new team member asks "why did we choose Supabase over Firebase?" and receives an ADR-grounded answer with traceability references in seconds. ## Quick Start Ask the assistant to run /spec-explain with a feature name like "notifications" or a natural language question such as "how does the real-time messaging system work?"
