Product Manager

### Quick judgement High-quality, principle-driven product management skill that encapsulates a strong practitioner mindset across the product lifecycle. Best suited for guiding thinking and decision-making rather than generating deeply tailored artifacts on its own. ### What it does well - **End-to-end coverage:** Addresses discovery, prioritization, roadmapping, requirements, working with engineering/design, stakeholder management, metrics, launch, and common mistakes. - **User/impact focus:** Repeatedly emphasizes talking to users, validating problems before solutions, and focusing on outcomes over outputs. - **Execution pragmatism:** Encourages ruthless prioritization, saying no, preventing scope creep, surfacing dependencies, and updating plans when reality changes. - **Cross-functional health:** Provides concrete norms for collaborating with engineering (context, tradeoffs, estimates) and design (research together, critique work, not people). ### Key risks / limitations - **Generic by design:** Principles are strong but abstract; users still need to translate them into domain- and company-specific processes, metrics, and constraints. - **Limited operational tooling:** The text describes *what* good looks like more than it provides structured templates, frameworks, or step-by-step workflows (e.g., full discovery plans, scoring models, detailed OKR/roadmap schemas). - **Potential overconfidence:** Without explicit caveats, the skill might present one style of PM practice as universally correct, which could clash with specific organizational realities (e.g., regulated industries, sales-led orgs). ### Recommended scenarios Use this skill when you: - Want a **thinking partner** to critique or improve your discovery, prioritization, or roadmap strategy. - Need help **framing decisions and tradeoffs** with stakeholders, engineering, or design. - Are a newer PM seeking **principle-based guidance** on how to avoid common pitfalls like feature factories, overspecification, or roadmap anti-patterns. It is less ideal as a purely mechanical generator of documents (e.g., full PRDs, detailed project plans) without additional prompts that supply company context, data, and constraints.