pm-clarify

Clarify vague product requirements into structured testable specifications.

46|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-clarify-konglong87
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-clarify
Source: https://github.com/konglong87/superPM/tree/main/skills/01-demand-insight/pm-clarify
Command: npx skills add https://github.com/konglong87/superPM --skill pm-clarify-konglong87

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps you turn an initial, possibly vague product需求 into a structured, unambiguous requirements list with clear scenarios, boundaries, exception handling, and measurable acceptance criteria.

Core Features & Use Cases

  • Requirement deepening with guardrails: Iteratively clarify each requirement one by one to avoid scope ambiguity and rework.
  • Structured fields for delivery-ready specs: Capture usage scenario, concrete user behaviors, boundary conditions, exception handling, and acceptance criteria.
  • Optional parallel validation (v2.0): Run parallel subagent-style checks for market benchmarking and technical feasibility to strengthen decision-making.
  • Fast start when inputs are missing: If no prior requirement research report exists, switch to a fast mode where you manually list core需求.

Quick Start

Ask the AI to run pm-clarify using your current initial需求 list, or first run /pm-demand if you haven’t prepared the requirement research report yet.

Frequently Asked Questions about pm-clarify

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

FAQPage Schema
How do I turn vague product requirements into testable acceptance criteria?▼

To turn vague product requirements into testable acceptance criteria, you iteratively clarify each need to define usage scenarios, boundaries, exception handling, and measurable conditions, outputting a structured markdown specification.

What is the best way to structure a requirements list with clear boundaries and exception handling?▼

The best way to structure a requirements list is to capture specific fields for each need, including usage scenarios, concrete user behaviors, boundary conditions, and exception handling, ensuring delivery-ready specifications.

Can I generate a markdown requirements specification without prior requirement research documents?▼

Yes, you can generate a markdown requirements specification without prior research by switching to a fast mode where you manually input core requirements for immediate clarification and drafting.

How do I validate technical feasibility and market benchmarks during product planning?▼

You can validate technical feasibility and market benchmarks during product planning by running parallel checks alongside requirement clarification to strengthen specification decision-making.

When do I need to clarify requirements scenario design before writing a markdown spec?▼

You need to clarify requirements scenario design before writing a markdown spec when you have an initial needs list that lacks defined boundaries, exception handling, and measurable acceptance criteria, preventing scope ambiguity.

Does requirement clarification rework scope ambiguity for delivery-ready specs?▼

Yes, requirement clarification reworks scope ambiguity for delivery-ready specs by iteratively deepening each requirement with guardrails to prevent rework and ensure measurable testability.