pm/requirement-penetration

Analyze user requirements using 5W2H questioning and a four-layer demand model.

553|50|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill pm-requirement-penetration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm/requirement-penetration
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/pm/requirement-penetration
Command: npx skills add https://github.com/echoVic/boss-skill --skill pm-requirement-penetration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product managers often accept surface-level feature requests without uncovering what users truly need, leading to misaligned PRDs and wasted development effort. This Skill provides a structured methodology to penetrate beyond explicit statements and identify implicit, latent, and delighter requirements before writing a PRD.

Core Features & Use Cases

  • Four-Layer Demand Model: Classifies requirements into explicit, implicit, latent, and delighter tiers to reveal needs users did not state or even realize.
  • 5W2H Deep Questioning: Systematically probes What, Why, Who, When, Where, How, and How Much, with repeated why-questioning to reach root motivations.
  • Priority Matrix Output: Produces a value-versus-cost P0-P3 priority matrix and a structured requirements analysis section ready for insertion into a PRD.
  • Use Case: When a stakeholder says "add a dashboard", apply this methodology to uncover the implicit need for real-time alerts, the latent need for exportable reports, and a delighter such as anomaly detection, then prioritize them for the PRD.

Quick Start

Ask the agent to apply the requirement penetration methodology to analyze a new feature request and produce the layered requirements analysis with a priority matrix.

Frequently Asked Questions about pm/requirement-penetration

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

FAQPage Schema
How do I analyze user requirements before writing a PRD?

Use a layered requirement analysis that separates explicit, implicit, latent, and delighter needs, then apply 5W2H questioning to probe motivations. The output is a structured analysis section with a P0-P3 priority matrix ready for the PRD.

What is the 5W2H method for requirement gathering?

5W2H probes seven dimensions: What, Why, Who, When, Where, How, and How Much. It reveals true motivations, usage scenarios, and willingness to pay, and works best when you ask why repeatedly to reach root causes.

How do I identify implicit and latent user needs?

Implicit needs come from things users assume or omit, inferred from context and phrasing. Latent needs are discovered through scenario walkthroughs, competitor analysis, and industry trend reasoning rather than direct user statements.

How do I prioritize product requirements by value and cost?

Plot each requirement on a value-versus-cost matrix. High-value low-cost items are P0 must-dos, high-value high-cost items are P1, low-value low-cost items are P2, and low-value high-cost items are deferred as P3.

When should I not use deep requirement penetration?

Avoid full penetration analysis for trivial bug fixes or well-specified change requests where requirements are already validated. The methodology adds the most value for ambiguous new feature requests and early-stage product discovery.