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 VP asks for a next-quarter roadmap recommendation across three options: improve onboarding, rebuild reporting, or add an AI assistant. Evidence is uneven: support mentions onboarding confusion, sales wants reporting, and leadership is excited about AI. No analytics, research notes, customer contracts, or engineering estimates are provided.
Without the bundle
Prioritize the AI assistant because it is strategically important and leadership is excited. Reporting can follow because sales wants it, and onboarding can be fixed later with smaller UX improvements. This output is intentionally weak: it treats stakeholder enthusiasm as evidence, does not inspect customer or metric sources, and creates a recommendation without decision criteria.
Using the bundle
Recommendation Do not commit a final sequence yet. Use a two-step decision: first validate onboarding and reporting evidence within one week, then choose the highest-confidence roadmap item. If a provisional plan is required today, place onboarding discovery first because it has a direct support signal and likely affects activation, but treat the AI assistant and reporting options as unresolved until evidence improves. Evidence Classes - User-provided evidence: support mentions onboarding confusion; sales wants reporting; leadership is excited about AI.
Why this is better: The bundle-assisted output is stronger because it avoids false certainty, separates evidence classes, compares tradeoffs, names missing verification, and gives a decision path. It still needs real local evidence before becoming a committed roadmap recommendation.
Inspect this example in the repositoryRole guide
Senior Product Manager
Defines the scope and expected behavior of a Senior Product Manager agent.
Read the fileWorkflow
Executive Roadmap Alignment
Turns competing roadmap options into executive-ready tradeoff and sequencing decisions.
Read the fileWorkflow
PRD and Requirements Review
Reviews product requirements for clarity, evidence, risks, acceptance criteria, and readiness.
Read the fileWorkflow
Product Metric Review
Interprets product metrics and reconciles conflicting sources before decisions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Senior Product Manager work, plus teams reviewing its decisions and outputs
- Teams working in software, saas, digital-products
When to use it
- A Senior 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 ambiguous product strategy and discovery decisions.
- Review roadmap tradeoffs for executive and cross-functional alignment.
- Improve PRDs and requirements before delivery work starts.
- Reconcile product metric conflicts without inventing definitions.
- Turn stakeholder disagreement into explicit options, risks, and decisions.
What it helps produce
- strategy brief
- roadmap decision memo
- PRD review
- metric interpretation memo
- stakeholder alignment memo
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 Senior Product Manager work by producing strategy brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with ESCO ICT product manager, then confirm that the reference is current and applicable. Inspect Senior Product Manager before drafting.
Context path: bundles/roles/senior-product-manager
What the bundle includes
Tools
- Jira
- Linear
- Confluence
- Notion
- Figma
- Amplitude
- Mixpanel
- Productboard
- Aha!
- spreadsheets
- BI dashboards
Frameworks
- Jobs-to-be-Done
- RICE prioritization
- Kano model
- opportunity solution tree
- OKRs
- North Star metric
- evidence-to-decision matrix
- product risk review
Commands
/draft-strategy-brief
/review-roadmap-tradeoffs
/review-prd
Evaluations
- senior-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 and seniority vary by organization; verify local ownership, decision rights, and escalation paths.
- This bundle does not replace legal, privacy, security, accessibility, medical, financial, procurement, or regulated-domain review.
- This bundle does not include authoritative tool-specific schemas, APIs, workspace fields, analytics definitions, or live system permissions.
- Taxonomy mappings are broad role adjacencies and should not be treated as a precise seniority-specific occupation code.
Safety notes
- Confirm before changing live product docs, tickets, roadmap systems, analytics definitions, feature flags, pricing, release notes, customer communications, or external commitments.
- Treat customer data, roadmap plans, product strategy, sales feedback, support tickets, and research notes as confidential unless the user confirms they are safe to use.
- Require qualified review for regulated-domain, legal, privacy, security, accessibility, medical, financial, employment, or contractual conclusions.