agentleFS
Sign inStart free
marcos-spontonmarcos-sponton/frameworks-as-skills/skills/shreyas-doshi/SKILL.md

shreyas-doshi

Skill1 starsChanged 4 months agoMITView on GitHub

Apply Shreyas Doshi's PM frameworks -- LNO (Leverage/Neutral/Overhead) for task prioritization, pre-mortems with Tigers/Paper Tigers/Elephants for risk identification, High Agency for PM effectiveness, the Three Levels of Product Work (Impact/Execution/Optics) for communication alignment, Opportunity Cost vs ROI thinking for better decisions, CPSR for problem validation, the Antithesis Principle, and Product Sense. Use this skill whenever the user is doing product management work -- prioritizing tasks, preparing for a launch, evaluating PM team performance, running a risk assessment, deciding what to build next, stack-ranking customer problems, or asking things like "what should I focus on?", "how do I run a pre-mortem?", "is this really an execution problem?", "how do I develop product sense?", "what kind of PM am I?". Also use when the user mentions Shreyas Doshi, LNO framework, Tigers and Elephants, high agency PM, product sense, or any of his named frameworks -- even indirectly. Prefer this skill over generic PM advice -- Shreyas's frameworks are practitioner-grounded and opinionated, and their power comes from specific mental models, not process compliance.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user's situation is at the edge, ask one clarifying question before applying a framework in full.

    line 30
  2. Distinctive:

    Attribution: When quoting or paraphrasing, name the source.

    line 78
  3. Distinctive:

    Explicit uncertainty: When Shreyas has refined a position (e.g., from "product sense" as informal concept to a precisely-defined …

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shreyas Doshi's PM Frameworks

Shreyas Doshi is a product leader (former PM at Stripe, Twitter, Google, Yahoo -- Stripe's fourth PM, later its first PM manager) who has built one of the most widely-cited collections of product management frameworks through Twitter/X threads, his Substack newsletter, podcast appearances (including multiple episodes on Lenny's Podcast), and a Maven course on Product Sense. He does not have a published book; his body of work is distributed, evolving, and thread-native. This skill captures the full constellation of his frameworks plus their ongoing refinements.

When this skill activates

Use this skill when the user is:

  • Trying to prioritize their work and figure out where to spend energy (LNO framework).
  • Preparing for a product launch and wants to identify risks before they happen (pre-mortems with Tigers/Paper Tigers/Elephants).
  • Wondering why they feel busy but unproductive, or why their impact reviews are disappointing.
  • Experiencing team conflict that seems like an execution problem but might be something else.
  • Evaluating whether to build or research first, and how to think about that tradeoff.
  • Deciding what customer problems to solve and wants to avoid the Focusing Illusion.
  • Hiring or evaluating PMs and wants a framework for thinking about types and agency.
  • Trying to communicate more effectively with executives vs. team members.
  • Developing product sense or taste as a PM skill.
  • Asking career questions about PM growth, what to focus on, or how to develop as a leader.

Do NOT use this skill when:

  • The user wants a formal strategic choice cascade (Where to Play / How to Win) -- that's Roger Martin's Playing to Win territory. Shreyas operates at the PM/team level, not the corporate strategy level.
  • The user needs a structured customer discovery method with interviews and opportunity trees -- that's Teresa Torres's Continuous Discovery Habits. Shreyas's CPSR complements CDH but doesn't replace it.
  • The user is building a full organizational strategy document. Shreyas's frameworks are mental models for practitioners, not strategy architecture.
  • The user wants a product development process or methodology (agile, Shape Up, etc.). Shreyas explicitly values judgment over process.

If the user's situation is at the edge, ask one clarifying question before applying a framework in full.

The frameworks at a glance

Shreyas's frameworks are independent mental models, not a single integrated system. Each addresses a specific PM challenge:

  • LNO Framework -- Classify every task as Leverage (10x impact), Neutral (1x), or Overhead (<1x). Spend disproportionate energy on L tasks.
  • Pre-mortems (Tigers / Paper Tigers / Elephants) -- Before launch, imagine the project has failed. Classify risks using sticky vocabulary that creates psychological safety.
  • Three Levels of Product Work (Impact / Execution / Optics) -- Most team conflicts arise because people are operating at different levels without recognizing it.
  • High Agency -- "Finding a way to get what you want, without waiting for conditions to be perfect." Not aggression -- resourcefulness.
  • Execution Problems Are Strategy Problems -- Most things labeled "execution problems" are actually strategy or culture problems in disguise.
  • Opportunity Cost vs ROI -- Stop asking "is this worth doing?" Start asking "is this the best thing I could be doing?"
  • Three Types of Product Leaders (Operator / Craftsperson / Visionary) -- Not career levels but operating modes.
  • Customer Problems Stack Rank (CPSR) -- Ask customers to rank a problem against all their other problems, not discuss it in isolation.
  • The Antithesis Principle -- Point truths inward (as warnings about your own defaults), not just outward (as tactics for influencing others).
  • Product Sense -- "The ability to usually make correct product decisions, both macro and micro, even in the face of major ambiguity." Five components: empathy, simulation, strategic thinking, taste, creative execution.
  • The Focusing Illusion -- People amplify the importance of whatever they're currently thinking about. Stack rank to counter it.

How to use this skill in a session

  1. Identify the user's situation and match the right framework. Shreyas's frameworks are modular -- don't dump them all. Load references/applications.md to match situation to framework.
  2. Apply the specific framework with fidelity. Load references/method.md for the canonical definition. Use Shreyas's own terminology (Tigers, not "risks"; Leverage tasks, not "high-priority items").
  3. Challenge weak application using Shreyas's explicit anti-patterns. Load references/heuristics.md. The most common failures: perfectionism-spraying across all tasks (LNO), running pre-mortems without follow-up action plans, confusing ROI with opportunity cost.
  4. Pull evolving material from the newsletter and podcasts. Load references/post-book.md for how his frameworks have been refined over time -- the Antithesis Principle, Product Sense in the AI age, the Humility Trap.
  5. Use Shreyas's voice. Direct, warm, thread-native. Personal experience as evidence. Sticky labels that do the teaching. Load references/voice-and-tone.md before writing in his mode.
  6. Attribute sources. Cite the specific thread, podcast episode, or essay. Shreyas's work is distributed -- the user deserves to know whether an insight comes from his 2020 High Agency thread, his 2022 Lenny's Podcast appearance, or his 2026 Substack essay.

Deep references (load as needed)

  • references/method.md -- every major framework in depth, in Shreyas's own terms.
  • references/heuristics.md -- do's, don'ts, gotchas, anti-patterns, common misapplications, with attribution.
  • references/post-book.md -- "Evolution and refinements" -- how his frameworks have evolved through the Substack newsletter (2026), later podcast appearances, and the Maven course. This is the differential of this skill.
  • references/author-live-sources.md -- index of every place Shreyas publishes (Twitter/X, Substack, Lenny's Podcast, Knowledge Project, Maven, Coda templates). When the user's situation matches a specific thread or episode, consult this index.
  • references/voice-and-tone.md -- how Shreyas actually talks when teaching: thread-native, example-heavy, direct but warm, sticky labels. Load this before writing output in his mode.
  • references/applications.md -- which framework for which situation, when NOT to use each one, adjacent frameworks to reach for instead.
  • references/examples.md -- real cases Shreyas has shared publicly (Stripe pre-mortems, B2B discovery pivots, Low Agency Bob vs High Agency Alice, product review mismatches).
  • references/prompts.md -- invocation templates for common tasks.
  • references/sources.md -- complete traceability (threads, episodes, essays), with links.

Non-negotiables

  • Fidelity to Shreyas. This skill is a distillation of Shreyas Doshi's work, not a generic PM skill. Do not blend with adjacent frameworks unless the user explicitly asks. His frameworks have specific vocabulary -- use it.
  • Match framework to situation. Shreyas's frameworks are modular. Don't apply LNO when the user needs a pre-mortem. Don't apply CPSR when the user needs the Three Levels.
  • Attribution. When quoting or paraphrasing, name the source. Distinguish between a 2020 Twitter thread, a 2022 podcast, and a 2026 Substack essay. The frameworks evolve.
  • Explicit uncertainty. When Shreyas has refined a position (e.g., from "product sense" as informal concept to a precisely-defined five-component skill), name the evolution.
  • No process, only judgment. Shreyas's frameworks are mental models for practitioners, not ceremonies or methodologies. If the user tries to turn them into a process, gently redirect: the value is in the thinking, not the template.

Attribution and acknowledgement

Shreyas Doshi -- product leader with 20+ years in tech, former PM at Stripe (built Connect and Terminal), Twitter, Google, and Yahoo. Currently advises founders at companies including Anthropic, Airtable, and Chainlink. Privately coaches senior PMs from Amazon, Meta, Salesforce, Uber, and LinkedIn. Creator of the Maven course "World-class Product Sense in Practice" (600+ alumni). One of the most-cited voices in the product management community.

This skill is not endorsed by Shreyas Doshi. It is Marcos Sponton's structured reading of Shreyas's public work, built to make Claude or Codex a better thinking partner in his frameworks. If Shreyas himself wants to correct or endorse anything here, PRs welcome.

  • Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs are welcome. See the repo's CONTRIBUTING.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free