pm-refine

Refine product requirement materials into a structured PMContext file.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-refine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-refine
Source: https://github.com/Wcof/PMSkill/tree/main/skills/discovery/pm-refine
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams turn scattered requirement inputs, research notes, code scan findings, and conflicting stakeholder statements into a single structured PMContext. It reduces ambiguity by forcing every important point into a clear status: fact, assumption, conflict, or pending confirmation.

Core Features & Use Cases

  • 8-dimension requirement refinement: Systematically covers user scenarios, boundary conditions, conflict detection, prioritization, terminology, current workaround friction, technical constraints, and success metrics.
  • Dual operating modes: Supports guided questioning for collaborative clarification with a PM, or autonomous inference with the --auto mode when fast end-to-end refinement is needed.
  • Traceable PMContext output: Produces a single self-contained PMContext file with confidence marking, information gaps, decision logs, and audit trails for downstream PRD, stories, and prototype generation.
  • Use Case: After collecting inputs from user interviews, support tickets, internal docs, and codebase scans, use this Skill to consolidate them into a reviewable PMContext before generating a PRD.

Quick Start

Ask the agent to run pm-refine on your collected materials to clarify the requirement, label confidence and gaps, and write a PMContext file.

Frequently Asked Questions about pm-refine

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

FAQPage Schema
How do I consolidate conflicting stakeholder requirements into a structured context?▼

You can consolidate conflicting stakeholder requirements by refining collected interview notes and documents into a structured PMContext. This process forces every important point into a clear status: fact, assumption, conflict, or pending confirmation.

What is the best way to clarify ambiguous product requirements before writing a PRD?▼

The best way to clarify ambiguous product requirements is to apply 8-dimension requirement refinement. This systematically covers user scenarios, boundary conditions, conflict detection, prioritization, terminology, friction, constraints, and success metrics.

How do I structure messy product discovery inputs with confidence scoring?▼

You structure messy product discovery inputs by running a refinement workflow that generates a single self-contained PMContext file. This output includes explicit confidence marking, information gaps, and decision logs for downstream workflows.

Can I automatically refine requirements without guided questioning?▼

Yes, you can automatically refine requirements without guided questioning by using the autonomous inference mode. This allows fast end-to-end refinement of research notes and codebase scans without collaborative PM clarification.

Does requirement refinement support traceable source attribution for audit trails?▼

Yes, requirement refinement supports traceable source attribution. It produces an audit trail with decision logging and confidence scoring to ensure every fact and assumption is reviewable before generating PRDs or prototypes.