product-manager

Define product requirements and prioritize feature decisions for software products.

19|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/bonnguyenitc/antigravity-superpowers --skill product-manager-bonnguyenitc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/bonnguyenitc/antigravity-superpowers/tree/main/.agent/skills/product-manager
Command: npx skills add https://github.com/bonnguyenitc/antigravity-superpowers --skill product-manager-bonnguyenitc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams define product requirements, prioritize features, and make roadmap trade-offs so work aligns with measurable user and business outcomes rather than output alone. It reduces wasted engineering effort by focusing on the smallest experiments that validate user problems and business impact.

Core Features & Use Cases

  • Outcome-oriented prioritization: Apply frameworks like ICE, RICE, and MoSCoW to score and rank ideas against clear success metrics.
  • Validation-first planning: Recommend minimal experiments, research patterns, and acceptance criteria to test demand before building.
  • Roadmap and scope guidance: Structure short cycles, identify "don't build" candidates, and surface red flags such as missing metrics or user research.
  • Use case: Turn a vague feature request into a validated mini-experiment, with success metric, acceptance criteria, and a recommended next step (build, buy, or don't-build).

Quick Start

Ask the product-manager to convert your feature idea into a prioritized 6-week plan with one measurable North Star, acceptance criteria, and suggested experiments before building.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I prioritize product features to ship measurable outcomes?

Feature prioritization uses frameworks like ICE, RICE, and MoSCoW to score and rank ideas against clear success metrics, ensuring roadmap decisions align with measurable user and business outcomes rather than output alone.

What is the best way to turn a vague feature request into a validated experiment?

Transform vague requests into minimal experiments by defining a measurable North Star, setting acceptance criteria, and using user research to recommend a build, buy, or don't-build next step.

How do I structure a roadmap and identify features I should not build?

Structure short roadmap cycles and identify don't-build candidates by validating demand through minimal experiments, which surfaces red flags like missing metrics or user research to reduce wasted engineering effort.

Do I need user research and metrics before making feature trade-offs?

Yes, feature trade-offs require outcome-focused metrics, user segmentation, and basic product analytics or user feedback to confidently recommend build, buy, or don't-build decisions for pre-PMF and post-PMF planning.

Can I use this for both pre-PMF and post-PMF product planning?

Yes, this supports both pre-PMF and post-PMF planning by guiding roadmap scoping and feature trade-offs through user segmentation, acceptance criteria, and outcome-focused metrics to validate user problems and business impact.