product-work-levels

Diagnose product work disconnects using Shreyas Doshi's three-level framework.

70|34|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill product-work-levels-productfculty-aipm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-work-levels
Source: https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/product-work-levels
Command: npx skills add https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill product-work-levels-productfculty-aipm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose why outcomes are disconnected from activity in product work by applying Shreyas Doshi's three-levels-of-product-work framework to help teams identify whether issues are at the outcomes (Level 1), strategy (Level 2), or execution (Level 3) level.

Core Features & Use Cases

  • Guided, step-by-step diagnosis across Level 1 (Outcomes), Level 2 (Strategy), and Level 3 (Execution).
  • Context-aware analysis that can reference memory and roadmap context to tailor recommendations.
  • Output-ready recommendations that include diagnosis, evidence, and actionable next steps for teams.

Quick Start

Explain your current frustrations and map them to Level 1, Level 2, or Level 3 using Shreyas Doshi's framework.

Frequently Asked Questions about product-work-levels

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

FAQPage Schema
How do I diagnose why product outcomes are disconnected from team activity?

To diagnose product-work misalignment between outcomes and activity, you can apply Shreyas Doshi's three-levels-of-product-work framework to scope issues to Level 1 outcomes, Level 2 strategy, or Level 3 execution. This generates targeted improvements, evidence, and next actions.

What is the three-levels-of-product-work framework for diagnosing strategy and execution issues?

The three-levels-of-product-work framework categorizes product issues into Level 1 outcomes, Level 2 strategy, and Level 3 execution. It helps teams diagnose why outcomes are disconnected from activity by providing a concise analysis with evidence and a recommended next action.

How do I identify whether my product problem is a Level 1, Level 2, or Level 3 issue?

You can identify your product work level by explaining your current frustrations and mapping them across outcomes, strategy, and execution. The framework scopes the analysis to the correct level and provides one clarifying question to refine the diagnosis.

Can I use this product-work diagnosis framework with existing roadmap context?

Yes, the diagnosis performs context-aware analysis that can reference memory and roadmap context. This tailors the recommendations to your specific situation, outputting a diagnosis with evidence and an actionable next step for your team.

What is the best way to generate targeted improvements for misaligned product work?

The best way to generate targeted improvements is a guided step-by-step diagnosis across outcomes, strategy, and execution. This approach outputs a concise diagnosis with evidence, a recommended next action, and one clarifying question to resolve misalignment.

When should I not use a Level 1 outcomes diagnosis for my product team?

You should not use a Level 1 outcomes diagnosis when the core problem actually stems from Level 2 strategy or Level 3 execution issues. The framework helps you scope the analysis correctly to avoid misdiagnosing the root cause of activity-outcome disconnection.