Defining minimum viable product
Skill casioreview20-glitch/forge-os/skills-v2/stable/defining-minimum-viable-product
Use when identify the smallest end-to-end product that tests the product thesis rather than a pile of disconnected features, especially when does the MVP deliver user value end to end?.From its SKILL.md
npx -y skills add casioreview20-glitch/forge-os --skill defining-minimum-viable-productAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
0.9 KB, 93 tokens by cl100k_base, as published. Nobody here has run it
Defining Minimum Viable Product
Core principle
Identify the smallest end-to-end product that tests the product thesis rather than a pile of disconnected features. Activate only when the typed entry conditions are present; stop rather than inventing a missing tool, decision, or proof.
When not to use
- a mature product requiring full release scope
- a prototype whose learning question is still unknown
Load only the sections selected by the RoutePlan.
What ships with it: 6 files
10.2 KB alongside SKILL.md
sections/
- decision-tables.md346 B
- examples.md373 B
- failure-modes.md276 B
- procedure.md751 B
- verification.md330 B
- manifest.json8.2 KB