mb-pm

Generate product requirements and acceptance criteria from codebase evidence.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Yanick-mj/mb-framework --skill mb-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mb-pm
Source: https://github.com/Yanick-mj/mb-framework/tree/main/agents/pm
Command: npx skills add https://github.com/Yanick-mj/mb-framework --skill mb-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to translate vague ideas into concrete, testable requirements, leading to misaligned expectations and rework.

Core Features & Use Cases

  • Requirements Generation: Synthesizes detailed functional requirements from feature descriptions, code context, and existing documentation.
  • Acceptance Criteria Drafting: Produces verifiable Given/When/Then criteria linked to user value and scope.
  • Scope & Evidence Management: Identifies in‑scope and out‑of‑scope items and backs each requirement with file paths and excerpts.

Quick Start

Ask the MB-PM skill to draft requirements for the feature “user authentication” using the current project documentation.

Frequently Asked Questions about mb-pm

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

FAQPage Schema
How do I generate testable product requirements from vague feature ideas?

To generate testable product requirements, synthesize feature descriptions with existing codebase context and documentation to produce detailed functional requirements backed by file path evidence.

How do I write acceptance criteria for sprint stories using Given/When/Then format?

Writing acceptance criteria for sprint stories involves drafting verifiable Given/When/Then statements directly linked to user value and defined scope boundaries extracted from project documentation.

What is the best way to define in-scope and out-of-scope items during product discovery?

Defining in-scope and out-of-scope items during product discovery requires analyzing existing backlog data and codebase files to identify boundaries and back each requirement with supporting evidence.

Can I use existing project documentation to draft requirements for new software features?

You can use existing project documentation to draft requirements by utilizing read, glob, and grep tools to collect evidence and synthesizing it into comprehensive functional specifications.

Why do my software development pipelines produce misaligned feature expectations?

Software development pipelines produce misaligned feature expectations when vague ideas are not translated into concrete, testable requirements with verifiable acceptance criteria and clear scope definitions.