tomaszstaniak/pm-ai-skills Skills

Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use when you need to: (1) build an opportunity solution tree from desired outcomes, (2) identify and prioritize customer opportunities, (3) design assumption tests for product ideas, (4) structure customer interview snapshots, (5) map assumptions to experiments, (6) move from output-driven to outcome-driven product development, (7) map current-state customer experiences, (8) build a weekly discovery habit.

Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use when you need to: (1) diagnose whether a team is stuck in the build trap (shipping features without outcomes), (2) shift from output-driven to outcome-driven product development, (3) evaluate product manager archetypes and team maturity, (4) design a product strategy that connects company vision to team-level decisions, (5) run a pre-mortem on a product roadmap to detect build-trap patterns.

Leadership transition framework based on Michael D. Watkins'' "The First 90 Days". Use when you need to: (1) plan onboarding for a new leadership or management role, (2) build a 30-60-90 day plan, (3) diagnose the business situation you''re entering (STARS model), (4) plan critical early conversations with your new boss, peers, and team, (5) identify and avoid common transition traps, (6) accelerate time to value in a new role.

Strategy evaluation and design framework based on Richard Rumelt''s "Good Strategy Bad Strategy" and Michael Porter''s "What Is Strategy?". Use when you need to: (1) evaluate whether a strategy is good or bad, (2) diagnose the core challenge before proposing solutions, (3) build a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-test strategic plans with pre-mortem analysis, (5) distinguish strategy from goals, ambitions, or wish lists.

Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use when you need to: (1) define or evaluate product positioning using the five-component framework, (2) translate positioning into a compelling pitch for stakeholders or buyers, (3) choose a market category strategy that shapes what you build and how you compete, (4) develop differentiated value claims that connect product decisions to market reality, (5) structure a pitch for exec reviews, board updates, or partner conversations, (6) diagnose why your product story isn''t landing with customers or internal stakeholders, (7) align cross-functional teams around a shared positioning narrative, (8) connect positioning decisions to roadmap priorities and feature trade-offs

Framework based on April Dunford''s "Sales Pitch". Use when you need to: (1) structure a B2B sales conversation that builds buyer confidence rather than pushing features, (2) develop a pitch narrative grounded in competitive positioning, (3) diagnose why deals are stalling or ending without decisions, (4) train sales teams on a consistent, repeatable pitch structure, (5) translate product positioning into a sales story, (6) help buyers navigate complex markets and evaluate trade-offs, (7) create pitch storyboards with cross-functional teams, (8) extend sales messaging to content, demos, and marketing materials

Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use when you need to: (1) write a PR/FAQ document for a new product or feature, (2) validate an idea by defining the customer experience first, (3) stress-test a proposal with pre-mortem analysis, (4) align stakeholders around a product vision, (5) decide whether an idea is worth building before writing code.