The workflow scoping doc.
One page. Five questions. Forces you to decide whether a workflow is worth building before you write a line of code. The same template our agency students charge clients $2,000 to fill out.
- FormatMarkdown
- Length1 page
- LicenseMIT
Five questions. One page. Hard answers.
The questions are deliberately rude. They're designed to kill bad workflows before you fall in love with them. If you can't answer all five in plain English, you don't yet have a workflow.
What does success look like in 90 days?
The number you'd put on a slide. If it's not a number, it's not success.
What's the workflow shape?
Single-turn, multi-turn, or graph. Pick one. The pick determines everything else.
What must it refuse?
Three things it must not attempt. If you can't write three, you don't understand the workflow yet.
What's the kill switch?
How do you stop the world in 60 seconds without a deploy. Be specific.
What's the eval?
The 20 cases that must pass. If you don't have 20, write them. They'll change as you build.