pm-stage-01-brief

Name: pm-stage-01-brief
Availability: InStock
Author: pingmepi

Generate a structured 7-section product brief from a business statement.

Updated Jun 8, 2026

Search Tags:#automation #strategy #product-management #brief #product-definition #pdlc

Ready to run

npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-01-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-stage-01-brief
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-stage-01-brief
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-01-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the ambiguity and lack of alignment in the early product definition phase by transforming raw business statements into structured, decision-bearing product briefs.

Core Features & Use Cases

Standardized Brief Generation: Automatically creates a 7-section product brief including problem, target user, and success hypothesis.
Context-Aware Synthesis: Integrates project wiki, codebase understanding, and modular context packs to ensure briefs are grounded in reality.
Gatekeeping & Validation: Enforces pre-stage hooks and approval workflows to prevent unapproved changes and ensure upstream consistency.

Quick Start

Invoke the pm-stage-01-brief skill to generate a product brief based on the current business statement and project context.

Frequently Asked Questions about pm-stage-01-brief

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

FAQPage Schema

How do I generate a structured product brief from a raw business statement?▼

Generate a structured product brief by automating the synthesis of a raw business statement into a 7-section document covering the problem, target user, and success hypothesis. This establishes the foundation for the entire product definition lifecycle.

What is the best way to align early product definition with upstream project constraints?▼

Align early product definition by integrating local PM-OS hooks and modular context packs with your project wiki. This ensures generated product briefs enforce upstream consistency and remain grounded in actual codebase understanding.

How do I enforce approval workflows and prevent unapproved changes during the initial PDLC stage?▼

Enforce approval workflows during the initial PDLC stage by applying pre-stage gatekeeping hooks. This validation mechanism prevents unapproved changes and ensures upstream decisions are consistently checked before product brief generation.

Do I need local context files to draft a product brief for scope and success metrics?▼

Yes, you need local context files to draft a product brief accurately. Context-aware synthesis integrates project wikis and modular context packs to ensure scope, target users, and success metrics are grounded in reality.

What sections are included in an automated product brief for product management?▼

An automated product brief includes a standardized 7-section structure covering the core problem, target user, and success hypothesis. This standardization solves ambiguity and lack of alignment in the early product definition phase.

Can I use product management automation to validate target users and success hypotheses before development?▼

Yes, you can use product management automation to validate target users and success hypotheses before development. The generated brief applies gatekeeping and validation workflows to ensure upstream consistency and prevent unapproved scope changes.