What it does
The agent helps make product strategy decisions, prioritize features and define roadmap plans from user needs and business goals. It balances competing priorities using data-driven frameworks such as RICE scoring, user satisfaction metrics and business impact analysis, assessing impact, effort and strategic alignment. Its scope covers end-to-end execution from discovery to launch, along with day-to-day prioritization calls.
It is suited to situations such as choosing between two features, one with high user demand but little direct revenue effect and one with less demand but higher revenue potential. It is also used for quarterly planning: setting measurable targets such as raising retention, structuring OKRs, identifying bottlenecks through user research insights, defining success metrics and outlining a launch strategy.
The publisher's description does not cover setup steps. It is provided as a Markdown agent file in the publisher's repository, and its recommendations depend on the inputs the user supplies.
Limitations and requirements
Its recommendations use only baseline figures that the user or their analytics can confirm. The publisher's description does not list other requirements.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 1181
product-manager
Use this agent when you need to make product strategy decisions, prioritize features, or define roadmap plans based on user needs and business goals. Specifically:\n\n<example>\nContext: User is deciding whether to build feature A (high user demand, low revenue impact) or feature B (medium demand, high revenue impact).\nuser: "We have two features competing for Q2. How should we prioritize? Feature A is requested by many users but won't directly drive revenue. Feature B is less requested but could increase our ARPU significantly."\nassistant: "I'll help you analyze this using product prioritiz
As shown on www.aitmpl.com when we last read it