mvp-validator

Validate feature requests against MVP PRD acceptance criteria and scope definitions.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/kamal-haider/GigLedger --skill mvp-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvp-validator
Source: https://github.com/kamal-haider/GigLedger/tree/main/.claude/skills/mvp-validator
Command: npx skills add https://github.com/kamal-haider/GigLedger --skill mvp-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MVP scope creep wastes time and creates misalignment between product plans and implementation.

Core Features & Use Cases

  • Scope validation: Quickly determine if a requested feature is in MVP scope or explicitly out of scope.
  • Decision guidance: Flag features that require roadmap items or additional PRD updates.
  • PRD alignment: Ensure proposals reference docs/02_mvp_prd.md and meet acceptance criteria.

Quick Start

Submit a feature request and I will validate it against the MVP PRD to confirm scope and acceptance criteria.

Frequently Asked Questions about mvp-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate if a feature request is in MVP scope?

MVP scope validation cross-references feature requests against the MVP PRD to determine if items are in-scope or out-of-scope. It checks proposals against acceptance criteria and flags items requiring roadmap updates.

What is the best way to prevent scope creep during feature planning?

Preventing scope creep involves enforcing reference to the MVP PRD document during feature planning. This process flags out-of-scope items, identifies roadmap additions, and guides decisions using acceptance and exit criteria.

How does MVP validation work with acceptance criteria?

MVP validation checks feature proposals against defined acceptance criteria in the PRD. It confirms whether requested changes meet the exit criteria or require additional PRD updates before implementation.

Can I use MVP scope checks during code reviews?

Yes, MVP scope validation applies during code reviews to verify implemented features match the PRD. It cross-references the code changes against MVP exit criteria to catch scope creep.

When do I need to update the PRD for a roadmap item?

You need to update the PRD when scope validation flags a feature as out-of-scope for the current MVP. These items are identified as roadmap additions requiring separate PRD updates before implementation.