# Build a product walkthrough

Use when: someone needs to understand or operate an existing product flow.

Inputs: the working build or source, the intended audience, one bounded task and captured screens.

Procedure:
1. Confirm the actual entry point and the result the user is trying to reach.
2. Walk the flow. Capture what happens after each meaningful action.
3. Write one instruction per step: action, expected result, and what to do if it fails.
4. Pair each step with its actual screen. Never replace a missing screen with a fictional product state.
5. Connect any hidden system behavior to the visible consequence it explains.
6. Add prerequisites, a restart path and the current limitations.
7. Review the complete walkthrough at a narrow viewport and with keyboard navigation.

Output: a linear walkthrough with stable step IDs, captions and source references, ready for an interactive guide or document.

Acceptance: a reviewer can follow the supplied task without relying on the author's memory. Every displayed product state has evidence.

---

From Curious Current · Make the product explain itself
Format: Portable procedure
Evidence: A public process recipe based on the capture, organize and publish workflow. This is a portable Markdown procedure, not an installed runtime skill.
Source: https://curiouscurrent.com/products/walkthrough-forge/

Free to download and adapt. Review and test changes in your own environment.