pm-grill

Extracts and stress-tests load-bearing assumptions from a PMContext document.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams rigorously challenge a PMContext before committing to execution. It identifies load-bearing assumptions, exposes weak logic, and turns vague risks into falsifiable failure conditions and cheap validation tests.

Core Features & Use Cases

  • Red-team assumption attacks: Separates critical assumptions from decorative ones, then uses a steelman-then-attack method to challenge only the assumptions that could kill the plan if wrong.
  • Structured confidence interrogation: Reviews PMContext across eight dimensions such as user scenario, substitutes, metrics, constraints, technical stack, and hidden assumptions to surface confidence gaps.
  • Decision-focused output: Produces a ranked Top 5 list of fatal gaps, each with a Fails if condition, a kill criterion, and the cheapest test to run this week.
  • Use cases: Use it before roadmap reviews, PRD sign-off, strategy debates, launch readiness checks, or whenever a team wants a hard-nosed red-team critique of product logic.

Quick Start

Ask the AI to use pm-grill on your PMContext to identify the top fatal assumptions, challenge them, and propose the cheapest falsification tests.

Frequently Asked Questions about pm-grill

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

FAQPage Schema
How do I red-team a product strategy to find fatal assumptions before launch?▼

Red-team product strategy by extracting load-bearing assumptions, steelmanning them, attacking their strongest form, and defining falsifiable failure conditions to prevent flawed execution.

How do you stress-test PRD logic to expose hidden risks and weak measurement criteria?▼

Stress-test PRD logic by applying an eight-dimension confidence interrogation across user scenarios, substitutes, metrics, constraints, and technical stack to surface confidence gaps.

What is the best way to validate critical product assumptions without high testing costs?▼

Validate critical assumptions by ranking fatal gaps by impact likelihood and test cost, then recommending cheap kill-criterion-based tests to run this week to falsify them.

Can I use assumption testing for roadmap debates and launch readiness checks?▼

Assumption testing works for roadmap debates and launch readiness checks by separating critical assumptions from decorative ones and challenging only those that could kill the plan.

Do I need a PMContext to perform a decision review and identify failure conditions?▼

Decision review requires reading PMContext to identify load-bearing assumptions, expose weak logic, and turn vague risks into falsifiable failure conditions and cheap validation tests.