pmai-meta

Challenges product assumptions and generates counterexamples, alternative models, and recommendations for design decisions.

4|Updated May 26, 2026
One-click install
npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-meta-yyg501
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmai-meta
Source: https://github.com/YYG501/PM-AI-Harness/tree/main/skills/meta
Command: npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-meta-yyg501

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When product discussions stall on vague goals, patchwork solutions, or conflicting mental models, this Skill forces structured meta-thinking: it surfaces the most dangerous premise, finds counterexamples, and proposes genuinely different product models instead of rephrasing what was already said. ## Core Features & Use Cases - Premise Challenge: Identifies the most dangerous assumption behind a direction and states what evidence would overturn it. - Judgment Model Building: Structures each session into a judgment statement, a fact/constraint/truth-source/assumption ledger, decision criteria, and model axes. - Real Fork Alternatives: Only when a true product-model fork exists, presents 2-3 alternatives with conditions, costs, and a recommendation, then stops for the PM to decide. - Use Case: A PM says "this design feels wrong, it's just repeating my words." The Skill reconstructs context, reframes the question as a judgment sentence, exposes the hidden premise, and returns concrete conclusions to the design workflow. ## Quick Start Ask the assistant to run /pmai-meta to deeply challenge the current product direction and find its blind spots.

Frequently Asked Questions about pmai-meta

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

FAQPage Schema
How do I challenge a product direction that feels like a patch?

Invoke the meta-thinking workflow to reframe the issue as a judgment sentence, separate facts from assumptions, and identify the most dangerous premise. It then produces counterexamples and, only if a real model fork exists, 2-3 alternative directions with costs and a recommendation.

What is a product judgment model in product management?

A product judgment model has five parts: a judgment sentence, a ledger of facts/constraints/truth sources/assumptions, decision criteria, the model axis where the problem is stuck, and optional model-level alternatives. It turns vague discussion into a decision the PM can actually make.

When should I use meta-thinking versus going straight to design?

Use meta-thinking when goals, target users, or success criteria are unclear, when solutions keep adding fields to old paradigms, or when the PM says something feels wrong. Small copy changes and mechanically determined choices should go directly to design.

Does this skill replace the product design workflow?

No. It is an internal judgment capability called on demand by the design workflow. It returns conclusions about objects, states, permissions, and pages back to design, and never writes specifications, creates parallel processes, or advances build state itself.

Why does the skill sometimes refuse to give multiple alternatives?

Alternatives only appear at genuine product-model forks where directions differ on objects, responsibilities, states, truth sources, or validation paths. For wording, layout, or reversible preferences within one model, it gives a single recommendation instead of manufacturing fake options.