Start from a manifest
The Markdown Handoff Kit contains a fictional specification, acceptance criteria, manifest and local SVG. Its manifest.md names every expected file. Compare that list with the extracted folder before opening a reader: missing assets are a packaging problem, not necessarily a rendering problem.
Walk the document like a recipient
Open README.md, follow the specification and its links to acceptance and manifest, then return. Check that the diagram resolves. Read the scope statement and look for open questions that should be answered before implementation. If you have a PDF or HTML copy, open that copy too: page breaks, text selection, headings and local images can change during export.
Use this sequence for your own handoff:
- List source files and assets in a manifest.
- Follow local links from the entry page, not only from a file manager.
- Check images, diagrams and code blocks.
- Open each exported format on another machine or in a fresh location.
- Mark untested items explicitly.
The kit includes source files only. It does not include a finished PDF or HTML file, so make those with a tool you trust and inspect the results. Aero Markdown does not automatically certify a folder. Its native export is still part of an app not publicly available yet.
For image failures, use the local-image guide; for choosing a handoff format, read sharing Markdown with a non-technical recipient.