pm-normalized-brief

Converts raw product input into a structured brief with defined components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert noisy product input into a structured Normalized Brief that clarifies the problem and streamlines intake for product teams.

Core Features & Use Cases

  • Structured brief: transforms raw requests into a one-line problem, impacted users, trigger evidence, business effect, priority hypothesis, and known unknowns.
  • Stakeholder alignment: reduces ambiguity by providing a single, shareable framing.
  • Use Case: when a PM needs to synthesize stakeholder feedback into an actionable brief ready for solutioning.

Quick Start

Provide raw requests and context to generate a normalized product brief.

Frequently Asked Questions about pm-normalized-brief

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

FAQPage Schema
How do I convert messy stakeholder requests into a structured product brief?

A normalized product brief transforms raw stakeholder feedback into a structured format with a one-line problem, impacted users, trigger evidence, and known unknowns. It reduces ambiguity by providing a single, shareable framing across product, design, and engineering.

How do I synthesize user feedback and requirements into a single actionable brief?

Synthesize user feedback and requirements by normalizing raw inputs into an actionable brief containing a one-line problem, impacted users, trigger evidence, business effect, and priority hypothesis. This structures stakeholder alignment for downstream solutioning.

Can I use a normalized brief to align product, design, and engineering teams?

Yes, you can use a normalized brief to align product, design, and engineering teams by providing a single, shareable problem framing. It standardizes trigger evidence and business effects, reducing ambiguity across cross-functional stakeholders.

What is the best way to frame product problems from noisy stakeholder input?

The best way to frame product problems from noisy input is to normalize raw requests into a structured brief. This extracts the one-line problem, impacted users, and trigger evidence to clarify the core issue and guide product framing.

Does generating a product brief require specific input formats or dependencies?

Generating a product brief requires no specific dependencies, only raw requests and context as input. Providing unstructured stakeholder feedback and user requirements is sufficient to generate a normalized, actionable brief.