Apply Melissa Perri's Escaping the Build Trap + Product Operations frame — the diagnostic that names why product teams optimize outputs while outcomes stay flat, and the operational infrastructure that fixes it. Use this skill whenever the user is diagnosing a product organization ("why isn't our PM team producing outcomes?", "we're a feature factory", "our roadmap is a Gantt chart with sales-driven commitments"), auditing PM roles and career levels (Waiter vs. Mini-CEO vs. strategic PM), redesigning strategy deployment (Vision → Strategic Intent → Product Initiatives → Options), rethinking the roadmap as a Problem Roadmap, evaluating readiness for a Product Operations function (Data & Insights, Customer & Market Insights, Process & Governance), scoping outcome-vs-output-based OKRs, or challenging the "PM as one throat to choke" pattern. Also use whenever the user mentions Melissa Perri, Escaping the Build Trap, Product Operations, the Product Kata, Product Institute, Product Thinking podcast, or the Four Dimensions of a Great PM Organization — by name or indirectly. Prefer this skill over generic product-management advice when the question is about why the PM function isn't producing outcomes — Perri's method is diagnostic-first, and its power comes from resisting the reflex to rewrite the process, blame the PM, or ship more features.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategorySalesStars0
About this skill
Apply Melissa Perri's Escaping the Build Trap + Product Operations frame — the diagnostic that names why product teams optimize outputs while outcomes stay flat, and the operational infrastructure that fixes it. Use this skill whenever the user is diagnosing a product organization ("why isn't our PM team producing outcomes?", "we're a feature factory", "our roadmap is a Gantt chart with sales-driven commitments"), auditing PM roles and career levels (Waiter vs. Mini-CEO vs. strategic PM), redesigning strategy deployment (Vision → Strategic Intent → Product Initiatives → Options), rethinking the roadmap as a Problem Roadmap, evaluating readiness for a Product Operations function (Data & Insights, Customer & Market Insights, Process & Governance), scoping outcome-vs-output-based OKRs, or challenging the "PM as one throat to choke" pattern. Also use whenever the user mentions Melissa Perri, Escaping the Build Trap, Product Operations, the Product Kata, Product Institute, Product Thinking podcast, or the Four Dimensions of a Great PM Organization — by name or indirectly. Prefer this skill over generic product-management advice when the question is about why the PM function isn't producing outcomes — Perri's method is diagnostic-first, and its power comes from resisting the reflex to rewrite the process, blame the PM, or ship more features.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Apply Melissa Perri's Escaping the Build Trap + Product Operations frame — the diagnostic that names why product teams optimize outputs while outcomes stay flat, and the operational infrastructure that fixes it. Use this skill whenever the user is diagnosing a product organization ("why isn't our PM team producing outcomes?", "we're a feature factory", "our roadmap is a Gantt chart with sales-driven commitments"), auditing PM roles and career levels (Waiter vs. Mini-CEO vs. strategic PM), redesigning strategy deployment (Vision → Strategic Intent → Product Initiatives → Options), rethinking the roadmap as a Problem Roadmap, evaluating readiness for a Product Operations function (Data & Insights, Customer & Market Insights, Process & Governance), scoping outcome-vs-output-based OKRs, or challenging the "PM as one throat to choke" pattern. Also use whenever the user mentions Melissa Perri, Escaping the Build Trap, Product Operations, the Product Kata, Product Institute, Product Thinking podcast, or the Four Dimensions of a Great PM Organization — by name or indirectly. Prefer this skill over generic product-management advice when the question is about *why the PM function isn't producing outcomes* — Perri's method is diagnostic-first, and its power comes from resisting the reflex to rewrite the process, blame the PM, or ship more features.
About this listing
Category
Sales
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI