Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
A structured playbook for solopreneurs to define and scope a Minimum Viable Product. It covers hypothesis formulation, a four-step feature cutting process, build-vs-buy decisions, and launch readiness criteria. The focus is on shipping the smallest thing that tests a real business hypothesis, then learning from it.
Instead of generic product advice, it provides explicit decision filters for each stage, reducing guesswork about what to build, fake, or cut entirely.
When to use it
- Deciding which features to cut before a first product launch
- Writing a one-page MVP scope document to prevent scope creep
- Choosing between building custom code and buying existing tools
- Setting measurable success metrics for the first 30 days post-launch
- Structuring a build schedule with risk-first sequencing
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: I want to plan my MVP for an automated client progress report tool for freelance developers
- 1Writes a testable hypothesis with a behavior signal and a revenue signal
- 2Labels all proposed features as must-have, nice-to-have, or cut
- 3Runs each feature through the four cuts: hypothesis, fake-it, sequencing, and delight
- 4Produces a one-page MVP scope document with must-haves, faked features, and launch criteria
- 5Defines post-launch success metrics and a Week 1 learning loop plan
A locked MVP scope document listing must-have features, manually-faked features, a cut list, a launch checklist, and 30-day success targets