pm-stage-02-scope

Generate a structured Product Scope document for the MVP phase.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-02-scope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-stage-02-scope
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-stage-02-scope
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-02-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the ambiguity of product definition by enforcing a structured, gated process to define the Minimum Viable Product (MVP) scope, ensuring alignment with business goals and preventing scope creep.

Core Features & Use Cases

  • Structured Scope Generation: Automatically drafts a Product Scope document based on approved business statements and briefs.
  • Constraint Validation: Integrates pre-stage gates to detect upstream drift and ensure all decisions are based on approved artifacts.
  • Use Case: A product manager needs to define the MVP boundaries for a new feature; this skill generates the scope document while ensuring all technical constraints and non-goals are explicitly documented and traced.

Quick Start

Run the pm-stage-02-scope skill to generate the product scope document for the current project stage.

Frequently Asked Questions about pm-stage-02-scope

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

FAQPage Schema
How do I define MVP scope for a new product feature without scope creep?

To define MVP scope without scope creep, this skill synthesizes approved business statements and product briefs into a structured Product Scope document, explicitly documenting technical constraints and non-goals to ensure alignment with business objectives.

How does PM-OS stage-gating validate product definition constraints?

PM-OS stage-gating validates product definition by integrating pre-stage gates that detect upstream drift, ensuring all scope decisions are strictly based on approved upstream artifacts to prevent ambiguity and misalignment.

How do I generate a structured product scope document for my project stage?

You can generate a structured product scope document by running this skill, which automatically drafts the MVP boundaries and traces dependencies using your approved business statements and local file system access for artifact generation.

Do I need approved business statements before defining product scope?

Yes, approved business statements and product briefs are required prerequisites before defining product scope, as this skill operates by synthesizing these upstream artifacts into defined scope, constraints, and dependencies.

What is the best way to document non-goals and constraints for an MVP phase?

The best way to document MVP non-goals and constraints is using a structured scope generation process that automatically drafts these boundaries while ensuring all technical constraints are explicitly documented and traced to approved artifacts.

Can I use local file system access for product scope artifact generation?

Yes, this skill requires local file system access for artifact generation, directly creating the structured Product Scope document on your local system during the product lifecycle MVP phase.