Prepare a fixed package
The Markdown Handoff Kit contains a fictional specification, acceptance checklist, manifest and local diagram. It includes source files only. If the real recipient needs PDF or HTML, create those outputs first and include the exact version you intend to send. Note the delivery method and app they will use.
Give tasks instead of a tour
Ask a participant to open the package, identify the first-version scope, find the diagram, locate an open question and explain what they would ask the author before implementation. Let them work without narrating where to click. Record task completion, confusion and the file or link involved. Avoid collecting private project content or screen recordings without informed consent.
If a participant cannot find a linked file, check whether it is missing from the ZIP, the link is broken, the viewer cannot open it, or the entry page does not make the path clear. Those causes lead to different fixes. The manual handoff checklist catches packaging faults before a session.
Report only observations you actually have
Write down participant role, environment, tasks, date and consent scope. Separate quotes and observed actions from your interpretation. With one person, describe a case rather than a general success rate. Repeat after changes if the result matters.
No recipient sessions were conducted for this article. It is a reusable protocol and sample package, not a case study claiming validated usability. Aero Markdown publishes this package as a reading example; it is not a benchmark result and not a claim about another app. The Mac app is not publicly available yet; this method works with the viewer chosen for the handoff.