Generate one coherent implementation story that explains how the code works end-to-end after the change.
Never include conversation process, investigation history, or request negotiation as walkthrough steps. The walkthrough must describe implementation behavior only. Never include full file dumps, raw secrets, credentials, tokens, private keys, or copied production payloads in the final output.
If runtime order and dependency order conflict, prefer dependency order and add one short transition sentence that reconnects to runtime flow.
Produces a single-story walkthrough of AI-authored code changes from runtime trigger to final behavior, weaving changed and unchanged code into one narrative with annotated diffs, trade-offs, alternatives, and risk analysis. Use when asked to "explain what changed", "walk me through this diff", "summarize agent edits", "show how this feature works", or "explain this implementation step by step". Source: cameroncooke/cameroncooke-skills.