Readiness
Readiness status prevents false handoff
- Ready to prototype is different from ready to build.
- Ready for developer review means questions are expected.
- Not ready is a valid decision when evidence or scope is weak.
Practice sequence
- 1Needs discoveryProblem or evidence still unclear.
- 2Ready to prototypeFlow or assumption needs lightweight testing.
- 3Ready for reviewDesign, feasibility, or accessibility needs review.
- 4Ready for buildScope, criteria, and handoff are clear enough to start.