Engineering Blueprint
Reverse-Engineer the PRD From Any Figma Design
Extract the hidden product spec from your Figma designs—surface missing states, implicit assumptions, and spec gaps before engineering starts building.
7 Files Included
inference-rubric.md
6 KB
command-reverse-prd.md
3 KB
What does this do
Designs and specs drift apart. Designers ship screens without specs and then face engineering asking "what is this supposed to do?" PMs review designs they didn't spec and need to verify the assumptions embedded in the frames. Engineers building from thin or outdated specs want structured confidence that their mental model matches the product intent before writing code. Founders shipping quickly need a forcing function to surface missing states and edge cases before launch. Reverse PRD bridges the gap by reading a design artifact — Figma frame, screenshot, or description — and writing the product spec it already implies: the user goal, user stories, success criteria, states covered, states missing, implicit assumptions about literacy, context, device, network, prior knowledge, attention budget, and permissions, and open spec questions. This gives each audience a usable first draft where they had nothing, or clarity on what's missing where they had uncertainty.
How It Works
Point the reverse-PRD skill at a Figma design (URL, frame, screenshot, or description). The skill reads the design artifact, infers the user goal and stories from visible affordances, catalogs which states the design covers and which it misses, surfaces seven categories of implicit assumptions (literacy, context, device, network, prior knowledge, attention budget, permissions), and generates a PRD document that engineering can use as a spec starting point. The output is a structured Markdown brief covering user goal, stories, success criteria, state inventory, missing states, assumption risks, and open questions for spec.
About This Blueprint
- Industry
- Information Technology