Filter project features to three and generate a 3-day MVP spec.
npx skills add https://github.com/epicsagas/epicsagas --skill mvp-force
Please help me install this Agent Skill. Skill: mvp-force Source: https://github.com/epicsagas/epicsagas/tree/main/skills/mvp-force Command: npx skills add https://github.com/epicsagas/epicsagas --skill mvp-force
MVP Force provides a disciplined gate for deciding whether a project can be shipped in 3 days at 50% effort, forcing a lean scope and preventing feature creep.
Describe your project and intended features in natural language, then invoke the MVP workflow to generate a lean 3-day MVP plan.
High-intent search queries and answers about installing and using this skill.
You can prevent feature creep by applying a survival filter to your project plan, reducing the feature list to at most three critical elements. This disciplined gate enforces a lean MVP scope by eliminating non-essential features early.
The 3-day MVP rule is a planning constraint that limits total development effort to three days by estimating one day of effort per surviving feature. It works by filtering your planned features down to a maximum of three critical elements.
You generate an MVP spec by listing all planned features, applying a survival filter to keep three or fewer critical elements, and estimating one day of effort per survivor. The result is a compact MVP scope with clear success criteria.
Yes, this MVP workflow is specifically designed for early-stage product plans with more than a handful of features. It guides teams through feature listing, survival filtering, and sprint-sizing to enforce a lean 3-day scope.
The best way to prune features is to map your planned list through a survival filter, retaining at most three critical elements. You then size the sprint by estimating one day of effort per surviving feature to meet the 3-day limit.
You should not use a 3-day MVP constraint when your project requires more than three critical features or cannot be delivered at 50% effort. It is designed for early-stage scoping and disciplined feature pruning, not complex, multi-sprint development.
FrkAkDecompose feature descriptions into detailed actionable tasks for software development projects.
alemdissoAnalyze GitHub Project #3 issues and Sprint Estimation Diary to generate day-by-day sprint plans.
AcidicSoilCalculate story points from Complexity, Effort, and Risk inputs.
mikeyfennelly1Evaluate new feature requests against MVP scope and impact criteria.
