Assumption Mapper Skill

Surface and prioritize the untested assumptions embedded in any product plan before development begins.

Required Inputs

Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).

• Product brief, PRD, or concept description (even rough notes work)
• Stage (concept / discovery / pre-build / post-launch — affects which assumptions matter most)

Where this sits — the spine's entry point