walkthrough — Phase 2: The Walkthrough Plan

Once the agent finishes execution and verification, it outputs a walkthrough artifact: a single Markdown file that lets you quickly catch up on what was changed and what is proven to work, and lets you do a staging-check with Git before merging.

This is modeled on Google Antigravity's walkthrough plan: the agent is expected to prove the change works (unit tests + real browser behavior), capture visual evidence, and hand you a review gate — not just dump a diff.

When to use

• After /goal (or any implementation) plus its verification pass are complete — e.g., after /review-it / /verify / manual testing
• Before /ship-it, as the last checkpoint before commit/PR/merge
• User says "walkthrough", "生成 walkthrough", "生成走查文档", "write the walkthrough", "/walkthrough", "Phase 2 walkthrough"

The Job