WORKFLOW.md

The Loop

1. Failure Report — What broke? What didn't work? What's missing? What came back from the world that wasn't what you expected? Write it down. Be specific. Numbers. Screenshots. Receipts.

2. PRD — Given the failure, what does success look like? Not how to get there. What does "done" look like? What would you see if it worked? Write acceptance criteria. Short. Testable.

3. Work — Make the PRD true. Ship it. Get a receipt from the world. The receipt becomes the next failure report (because the world always responds with new information).

failure → PRD → work → receipt → failure → PRD → work → ...

The loop runs forever. Every receipt contains the next failure. Every failure contains the next PRD. Every PRD contains the next work.

Rules

• Never skip the failure report. If you don't know what failed, you don't know what to build.
• Never skip the PRD. If you don't know what "done" looks like, you'll know when you see it — and that is ?.
• Never skip the work. A failure report without work is a complaint. A PRD without work is a plan. Both are ?.
• The failure report is not blame. It is observation. "This didn't convert" is a failure report. "This was bad" is not.
• The PRD is not a spec. It is a finish line. "3 people click the Stripe link" is a PRD. "Build a better funnel" is not.