Act as a thoughtful product management specialist. The task is feature request triage. Context: [feature request, user segment, current workflow, evidence].
1. Restate the underlying job to be done.
2. Assess frequency and severity.
3. Propose three solutions including no-build.
4. Set the evidence threshold for putting it on the roadmap..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Give a team enough clarity to build without a novel.
Act as a thoughtful product management specialist. The task is prd one-pager. Context: [problem, users, constraints, success measure].
1. Write problem, goal, non-goals and user stories.
2. Define acceptance criteria and edge cases.
3. List dependencies and open questions.
4. Make a rollout and measurement plan..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is roadmap tradeoff matrix. Context: [candidate projects, team capacity, goals, deadlines].
1. Define impact, confidence, effort and strategic fit scores.
2. Show the scoring table and sensitivity to uncertain inputs.
3. Choose a sequence.
4. Name what you are explicitly not doing..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Find patterns without laundering anecdotes into data.
Act as a thoughtful product management specialist. The task is user interview synthesis. Context: [interview notes, research question, sample size].
1. Tag observations separately from interpretations.
2. Cluster repeated pain points and exceptions.
3. Quote evidence with participant labels.
4. Write conclusions with confidence and unanswered questions..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Connect the north-star number to actions a team can take.
Act as a thoughtful product management specialist. The task is product metric tree. Context: [product, business goal, user journey, available events].
1. Choose an outcome metric and leading drivers.
2. Draw a text tree.
3. Define event names and denominators.
4. List ways the metrics could be gamed..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Find the last-mile gaps before a feature goes live.
Act as a thoughtful product management specialist. The task is launch readiness review. Context: [feature, audience, rollout date, systems touched].
1. Check quality, docs, support, analytics and rollback readiness.
2. Mark owner and status for each.
3. Define a go/no-go threshold.
4. Write first-week monitoring questions..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is experiment design sheet. Context: [hypothesis, target segment, baseline, intervention].
1. Define primary and guardrail metrics.
2. Choose unit of randomization and duration.
3. List confounds and minimum sample to calculate.
4. Write win, lose and inconclusive decision rules..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is churn interview guide. Context: [product, departed segment, cancellation data].
1. Write neutral questions on trigger, alternatives and last-use experience.
2. Avoid leading them toward your pet theory.
3. Make a coding sheet for patterns.
4. Separate fixable churn from bad-fit customers..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is prioritization meeting agenda. Context: [projects, stakeholders, decision owner, time].
1. Circulate evidence and criteria in advance.
2. Timebox each option's case and objections.
3. Record decision, dissent and revisiting trigger.
4. Write a concise outcome note..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Explain why this product exists for a particular user.
Act as a thoughtful product management specialist. The task is product positioning sentence. Context: [product, segment, alternatives, proof].
1. Draft five positioning lines with distinct wedges.
2. Test each for specificity and credibility.
3. Choose one with tradeoffs.
4. Adapt it into landing-page copy..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
See where intent leaks between discovery and value.
Act as a thoughtful product management specialist. The task is customer journey map. Context: [user persona, journey stages, data, feedback].
1. Map goals, actions, emotions and friction at each stage.
2. Identify the biggest drop-off hypothesis.
3. Propose fixes ranked by test cost.
4. Define one research task to validate..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is bug versus enhancement gate. Context: [report, expected behavior, spec, impact].
1. Write a decision tree based on promised behavior and harm.
2. Assign severity and reproduction steps.
3. Separate workaround from fix.
4. Set escalation criteria..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is beta feedback loop. Context: [beta cohort, feature, expected behavior, feedback channels].
1. Choose a small diverse cohort.
2. Write onboarding and feedback questions.
3. Create a daily issue triage.
4. Define graduation and rollback signals..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is product sunset plan. Context: [feature, usage, dependencies, alternatives, notice period].
1. Map affected segments and data export needs.
2. Plan notice and support windows.
3. Write migration paths and communication drafts.
4. Define a rollback window..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is internal tool adoption. Context: [tool, current workflow, users, resistance].
1. Identify the job it saves and the friction it adds.
2. Choose a pilot champion and use case.
3. Write a 30-minute onboarding.
4. Measure adoption and task completion, not logins..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Tell users what changed in language they care about.
Act as a thoughtful product management specialist. The task is release notes that matter. Context: [changes, users, impact, known limits].
1. Group updates by outcome rather than internal tickets.
2. Write a short headline and before-after example.
3. Surface changed behavior and next steps.
4. Keep technical detail available but secondary..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful product management specialist. The task is support ticket product signal. Context: [ticket themes, volume, user tiers, time period].
1. Normalize duplicates and segment by root cause.
2. Score frequency, severity and revenue exposure.
3. List qualitative examples with IDs.
4. Propose research before a large build..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Save a deadline by cutting carefully, not randomly.
Act as a thoughtful product management specialist. The task is scope cut workshop. Context: [project, deadline, must-haves, dependencies].
1. Map features by value and build coupling.
2. Choose a smallest coherent release.
3. Name deferred parts and user-facing consequences.
4. Write acceptance and release criteria..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Report product progress without hiding uncertainty.
Act as a thoughtful product management specialist. The task is stakeholder update. Context: [workstream, metrics, decisions, blockers].
1. Lead with outcome and evidence.
2. Separate shipped, learned and still uncertain.
3. State one decision needed with deadline.
4. Include the next visible checkpoint..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Decide what the release taught you after the confetti.
Act as a thoughtful product management specialist. The task is post-launch learning review. Context: [launch goals, metrics, feedback, incidents].
1. Compare intended versus observed outcomes.
2. Separate adoption from satisfaction and business impact.
3. List surprises and causes to investigate.
4. Choose continue, iterate or revert with an owner..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.