mvp-scoper

Scoping an MVP to a 4-6 week timeline requires classifying all extracted features into MUST, SHOULD, COULD, and WON'T categories using the MoSCoW method. This locks a 3-5 step critical path and generates an MVP-SPEC.md detailing vision, timeline, and constraints to prevent feature creep.

The MoSCoW method for feature pruning categorizes extracted product inputs into MUST, SHOULD, COULD, and WON'T lists. It applies founder-type pushback to isolate a 3-5 step critical path, explicitly pruning non-essential features to lock a strict 4-6 week MVP timeline.

Generating an MVP specification document involves running a 6-phase guided scoping process that extracts features, applies MoSCoW classification, and locks a realistic timeline. It outputs a comprehensive MVP-SPEC.md file detailing core vision, critical path, feature lists, success metrics, and constraints.

Yes, this MVP scoping process is designed for early-stage team environments and solo founders. It enforces timeline discipline and risk control by applying founder-type pushback across 6 phases, ensuring teams avoid feature creep and lock realistic 4-6 week schedules.

You should avoid locking a 4-6 week MVP timeline if your project requires extensive features outside a strict critical path. The scoping process enforces timeline discipline by explicitly listing WON'T build features, meaning projects needing broad initial scope will face heavy feature pruning constraints.