ship-decisions
Binary go/no-go shipping decisions using reversibility analysis (one-way vs two-way doors) and technical debt trade-offs. Use when user asks 'should we ship this now,' 'ready to ship,' 'one-way door,' 'two-way door,' or 'tech debt vs shipping.' For defining craft levels and deciding what to polish vs defer, see quality-speed. This is the ship decision methodology.
Inputs
- Source content or context for the selected route
How you ask
- Should we ship this feature or iterate more?
- Is this a one-way door or two-way door decision?
- Balance the technical debt against shipping speed
- Help me decide: ready to ship or needs more work?
Outputs
- hold-decision (markdown)
- readiness-brief (markdown)
- ship-decision (markdown)
Levelbeginner
Inputconversation
Outputdocument
Setup[none]
Roles[CEO / Founder, Product Manager]