walkthrough
Guided Walkthrough
Show what the work does, why it is useful, and how someone can try it. Support browser apps, desktop tools, terminal workflows, and noninteractive outputs. Use the current task as the scope; a walkthrough request does not imply a new implementation, deployment, or a full test matrix.
Choose and verify the story
Identify the audience, benefit, and shortest useful path from the request and project docs. Ask only when a missing choice changes the demonstration. For a prototype, explain the design choices and identify mocked data. For completed work, demonstrate the observable result and its limitations.
Discover the current environment from the repository or running application: launch instructions, URL, worktree, inputs, and authorized account. Read its local development instructions when starting services. Do not use remembered ports or record IDs. Choose existing safe example data and inspect it first. Do not reset databases or seed broad datasets just to improve the story.