pm-advisor-cagan

Analyzes product decisions using Marty Cagan's four-risk and empowered-team frameworks.

187|12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Luyu2026/Skill-Bible --skill pm-advisor-cagan-luyu2026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-advisor-cagan
Source: https://github.com/Luyu2026/Skill-Bible/tree/main/pm-advisory-suite/pm-advisor-cagan
Command: npx skills add https://github.com/Luyu2026/Skill-Bible --skill pm-advisor-cagan-luyu2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product managers often face recurring questions about whether a requirement is worth building, how to structure teams, and how to run product discovery, and end up rethinking each case from scratch. This Skill applies Marty Cagan's product operating model, distilled from Inspired, Empowered, Transformed, and SVPG essays, to give consistent, framework-grounded answers. ## Core Features & Use Cases - Four-Risk Review: Classifies any requirement by value, usability, feasibility, and business viability risk, then recommends the matching low-cost validation method. - Team Diagnosis: Distinguishes feature teams from empowered product teams and identifies whether the root cause is the problem handed to the team, not the people. - Strategy and Discovery Guidance: Challenges roadmap-as-strategy thinking and enforces discovery-before-delivery with 7 decision heuristics. - Use Case: You are debating whether to build a requested feature. The Skill reframes it as a user problem, locates the biggest risk among the four, and tells you what to validate before scheduling development. ## Quick Start Ask the assistant to analyze your product requirement or team situation from Marty Cagan's perspective, pasting your JD, roadmap, or team context.

Frequently Asked Questions about pm-advisor-cagan

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

FAQPage Schema
How do I decide whether a product requirement is worth building?▼

Classify the requirement by its biggest risk among value, usability, feasibility, and business viability. If value risk dominates, run cheap discovery like prototype tests or user interviews before scheduling development, since backlog items are unvalidated assumptions.

What is the difference between a feature team and an empowered product team?▼

A feature team receives a list of features to build and is accountable only for output. An empowered product team receives a problem and a business outcome, decides the solution itself, and is accountable for results.

Does this framework apply to outsourcing or heavily regulated companies?▼

The model assumes a technology product company aiming for continuous innovation. It adapts poorly to project-based outsourcing, heavy compliance, pure growth marketing, or long hardware cycles, where empowerment and rapid discovery face structural limits.

Can the Skill predict what Marty Cagan would actually say about my product?▼

No. It infers answers from his published books and SVPG articles and states that responses are inference, not his real judgment. It declares this disclaimer once on first activation.

Why does the Skill say my roadmap is not a strategy?▼

Cagan's model treats a roadmap as a prioritized feature wishlist, not a strategy. A real strategy requires focus on a few priorities backed by market and data insights, and must state what you deliberately choose not to do.