Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
A SaaS team says support tickets show that new admins struggle to invite teammates during onboarding. Draft a PRD for improving team invitation setup. Assume no direct access to support tools, analytics, customer interviews, or engineering systems unless the user provides data.
Without the bundle
Build a better invitation flow so admins can invite teammates more easily. Add clearer buttons, email validation, and reminders. Success should be more invitations sent and fewer support tickets. Engineering should build this next sprint. This output is weak because it invents urgency, implementation scope, success definitions, and delivery timing without evidence.
Using the bundle
Summary Current hypothesis: new workspace admins may be failing or delaying teammate invitations during onboarding. A PRD is not ready for commitment until support ticket examples, onboarding funnel data, and current invitation-flow constraints are verified. Problem User-provided evidence says support tickets mention admin difficulty inviting teammates. Missing evidence: ticket volume and themes, onboarding step analytics, affected segments, current UI, permission model, email deliverability constraints, and support severity. Draft Goals - Reduce invitation setup friction for new admins. - Improve activation evidence tied to successful team setup.
Why this is better: The bundle-assisted output is stronger because it refuses to convert a vague support-ticket claim into a committed build plan. It separates user-provided evidence from assumptions, defines missing verification, narrows scope, identifies review needs, and includes a source note.
Inspect this example in the repositoryRole guide
Product Manager
Defines the scope and expected behavior of a Product Manager agent.
Read the fileWorkflow
Define Product Opportunity
Turn product context and evidence into a decision-ready opportunity frame.
Read the fileWorkflow
Prioritize Roadmap
Compare roadmap options while preserving evidence quality and uncertainty.
Read the fileWorkflow
Review Product Metrics
Interpret product metrics with source discipline and no invented definitions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Product Manager work, plus teams reviewing its decisions and outputs
- Teams working in software, saas, digital-products
When to use it
- A Product Manager task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- frame product opportunities
- draft product requirements
- prioritize roadmap options
- review product metrics
- align stakeholders on product decisions
What it helps produce
- product brief
- product requirements document
- roadmap narrative
- opportunity assessment
- metric review
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Product Manager work by producing product brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 11 2021.00, then confirm that the reference is current and applicable. Inspect Product Manager before drafting.
Context path: bundles/roles/product-manager
What the bundle includes
Tools
- Jira
- Linear
- Confluence
- Notion
- Figma
- Amplitude
- Mixpanel
- Productboard
- Aha!
Frameworks
- Jobs-to-be-Done
- RICE prioritization
- Kano model
- opportunity solution tree
- North Star metric
- Scrum
Commands
/draft-product-brief
/review-prd
/prioritize-roadmap
Evaluations
- product-management-quality-check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Product management scope varies by organization; verify local ownership, process, and decision rights.
- Does not replace legal, privacy, security, accessibility, finance, medical, or regulated-domain review.
- Does not include tool-specific API or workspace configuration details.
- The O*NET/ESCO mapping comes from the reviewed generator candidate and should be treated as taxonomy context, not a complete definition of modern product management.
Safety notes
- Confirm before modifying live product docs, tickets, roadmap systems, analytics definitions, feature flags, pricing, release notes, or customer communications.
- Treat customer data, roadmap plans, product strategy, sales feedback, and research notes as confidential unless the user confirms they are safe to use.
- Escalate legal, privacy, security, accessibility, medical, financial, employment, and regulated-industry requirements to appropriate experts.