tlc-prd
TLC PRD
Find out where this effort actually is. Understand the problem. Decide whether to solve it. Write that down as a PRD file, and stop.
SITUATION ────→ PROBLEM ───────→ VERDICT ───────→ FILE
(where this (no solution (a stop, or a (.prd/<slug>.md,
effort is) proposed yet) short record) nothing else)
These are not a script, they are the prerequisite order. Ask whatever is answerable given what is settled, and stop when nothing answerable is left. Whether has where we are as a prerequisite. Marching the sections as a form is how a PRD asks an effort that never shipped what its problem costs today.
The failure that matters is converging early: proposing a solution on turn two, hearing "sure", and manufacturing a decision. Everything below exists to make that harder.
The artifact is one Markdown file a product person can read and hand to someone else without having been in the room. It records the bet. It does not record how to build it.