What problem does it solve? After a saga implements substantial changes across files and components, an architect who doesn't read the underlying code needs to verify what happened without diffing everything. This Skill walks the architect through the changes via incremental narration, ending with a protocol of concrete decisions to act on. ## Core Features & Use Cases - Reactive Narration: No fixed agenda — after every architect signal, the narrator updates a model of what the architect knows and cares about, then picks the next most valuable topic. - Verify-First Discipline: Before stating that something was done a certain way, the narrator reads the actual code or commit history instead of quoting executor summaries. - Decision Protocol Output: Produces output/decision-protocol.md containing only actionable decisions with explicit user citations, while unresolved discussion traces stay in work/. - Use Case: After an automated saga lands changes across a dozen files, run a walkthrough session where the architect listens, asks questions, and pushes back — ending with a concrete list of what to change in specs, code, or tests. ## Quick Start Walk me through the changes this saga just landed, one idea at a time, and produce a decision protocol of what I need to act on.