product-superpowers

Use when analyzing competitors, understanding competitive landscape, conducting SWOT analysis, or positioning your product against alternatives.

Use when setting up or improving a continuous product discovery practice with weekly customer interviews.

Use when preparing design specifications for engineering handoff and quality assurance.

Use when planning a product or feature launch and preparing go-to-market execution.

Use when you have raw user feedback from multiple sources (interviews, surveys, tickets, reviews) and need to extract themes, patterns, and actionable insights

Use when defining product metrics, designing experiments, analyzing feature adoption, or setting up measurement frameworks.

Use when starting any conversation — before ANY response including clarifying questions

Use when completing PM artifacts (PRDs, user stories, roadmaps) or before sharing with stakeholders to verify quality and completeness

Use when executing PM plans with independent tasks — dispatches subagent per task with review between each

Use when facing 2+ independent research, analysis, or investigation tasks that can run concurrently without shared state

Use when presenting PM artifacts visually — OSTs, story maps, roadmaps, prioritization matrices, or competitive landscapes

Use when prioritizing or scoring features, user stories, or initiatives against each other.

Use before any product work — new features, product ideas, or behavior changes. Use before writing PRDs or user stories.

Use when defining or refining product vision, mission, strategic trade-offs, build-vs-buy decisions, or product-market fit assessment.

Use when creating or updating a product roadmap, defining OKRs, or communicating product direction to stakeholders.

Use when you need to update stakeholders, write executive summaries, manage cross-functional relationships, or resolve conflicts with engineering and design.

Use when you have an approved PRD and need to break it into actionable user stories for development.

Use when you have an approved discovery document and need to write a Product Requirements Document before implementation begins.