You need themes and actions from raw research data.

You need to define a test for a product hypothesis.

You need to plan, size, and structure an A/B test.

You need to choose the right statistical test and interpret results correctly.

You need to measure causal impact when you can't run a randomized experiment.

You need to analyze retention patterns and diagnose churn by cohort.

You need to diagnose conversion funnel drop-offs and prioritize fixes.

You need to design a dashboard with KPI hierarchy and alert thresholds.

You need to assess data quality across pipelines, metrics, and analytics surfaces.

You need objectives and KRs that are motivating, realistic, and measurable.

You need a PRD draft from a problem statement.

You need a complete story with acceptance criteria — optionally generate a UI prototype, review with stakeholders, and push to Linear, Jira, Asana, or Notion.

You want to stress-test a story before planning or build.

One story is too large and needs vertical slicing.

You need to clean, evaluate, or reorder backlog items.

You need a draft plan for iteration planning.

You need a fast status/blocker prep before standup.

You need a clean iteration summary for stakeholders.

You need concise stakeholder talking points and asks.

You need RICE prioritization scoring for a set of features or initiatives.

You need a jobs-to-be-done analysis for a product or feature area.

You need to identify risks and failure modes before committing to a plan.

You need a sprint summary pulled from GitHub commits instead of self-reports.

You need a stakeholder-ready roadmap divided into Now/Next/Later — optionally generate a branded deck and share via Slack, Miro, FigJam, or Notion.

You need to plan user interviews with a structured guide, capture template, and synthesis plan.

You need to connect a desired outcome to opportunities, solutions, and assumption tests using the Teresa Torres OST framework.

You need to prioritize features or initiatives on a 2x2 matrix (effort/impact, urgency/importance, or custom axes).

You need to categorize requirements into Must Have, Should Have, Could Have, and Won't Have for a release or scope boundary.

You need to organize stories into a visual story map showing the user journey with release slices.

You need to audit or create an information architecture.

You need an interview script for user research.

You need to synthesize interview findings into structured insights.

You need to map the customer journey across touchpoints.

You need to write a user story following the k8 standard.

You need a metrics framework connecting product, growth, and revenue with KPI hierarchy and review cadence.

You need to define or validate the team's North Star Metric with input metrics and business games.

You need to prepare and facilitate an OKR workshop.

You need to draft a PRD through guided questions.

You need to review a PRD against quality standards.

You need to prioritize backlog items using structured methods.

You need a product-facing changelog entry.

You need to reframe a roadmap around outcomes instead of outputs.

You need grab-and-go user stories for common MVP patterns.

You need a facilitated story writing session from persona to export.

You need to create user persona profiles from research.

You need to spec an AI-powered feature covering model requirements, prompt architecture, quality bar, cost projections, and guardrails.

You want to prototype a product feature using AI coding tools (Bolt, Lovable, v0, Replit, Cursor, Claude Code).

You need evaluation criteria and test harnesses for an AI-powered feature – quality rubrics, golden datasets, eval pipelines, and pass/fail thresholds.

You need to improve how new users reach their first moment of value.

You need to define actionable audience segments with activation criteria.

You need to prepare stories for the upcoming iteration through refine, split, write, and review.

You need a marketing-focused customer journey map across the full funnel.

You need to turn raw user feedback into reframed problems and segment hypotheses.

You need to model growth loops, levers, sensitivity analysis, and realistic projections.

You need to design a multi-channel notification system with frequency controls and engagement metrics.

You need to diagnose and optimize conversion funnels from UX audit through experimentation.

You need to build a personalization strategy from basic rules to 1:1 dynamic content.

You need to create a PRD from scratch through discovery questions, interview-driven writing, and review.

You need a visibility operating model for a product team.

You need a full Event Storming to Boris to SNAP architecture discovery workflow.

You need to model service relationships from Event Storming outputs.

You need to facilitate an Event Storming session.

You need to document APIs, data, integrations, events, stories, and risks per bounded context.

You need a high-level architecture or system diagram.

You want security-focused scenario and criteria analysis.

You need characterization tests on legacy behavior first.

You want failing tests generated from acceptance criteria.

You want minimum implementation for existing failing tests.

You want a safe refactor path with test checkpoints.

You want structured review feedback tied to standards.

You need a hypothesis-driven debugging flow.

You need docs and comments updated alongside a code change.

You need to plan or audit SRE instrumentation for reliability and operational health.

You need to plan or audit product observability for user behavior and outcomes.

You need to plan monitoring for LLM-powered features in production – quality metrics, cost tracking, drift detection, and alerting.

You need to choose the right AI model for each job in your product – model mapping, routing, cost modeling, and migration planning.

You need to decompose a feature description into structured technical signals – systems, services, data entities, backend actions, and event triggers.

You need to retrieve verified architecture context – actual services, databases, event streams, and owning teams.

You need to map verified services to code repositories, service root paths, and maintainers.

You need to extract evidence-based code dependencies and map the critical path and independent work streams.

You need a structured blameless postmortem for a production incident – timeline, contributing factors, action items, and facilitation guide.

You need to assess, categorize, and prioritize technical debt with a remediation roadmap and stakeholder summary.

You need to plan a system migration – pattern selection, risk mitigation, data validation, cutover checklist, and rollback strategy.

You need to document an architecture decision with context, alternatives, trade-offs, and consequences in standard ADR format.

You need to assess developer experience – tooling friction, CI/CD health, code review bottlenecks, knowledge access, on-call burden, and cognitive load.

You need a STRIDE-based threat model for a system or application with threat matrix and prioritized mitigations.

You need a security incident response plan with severity levels, playbooks, roles, and notification timelines.

You need a 6-18 month technology roadmap connecting business strategy to technical investments.

You need to evaluate build, buy, or adopt decisions with TCO analysis and scored comparison.

You need SLA frameworks with metrics, targets, measurement methodology, and governance.

You need to evaluate site crawlability, speed, and indexation health.

You need a cross-modal diagnostic review that maps code into sensory models to surface hidden architectural issues.

You need side-by-side analysis of competitor products.

You need to synthesize research data into a structured user persona for the team to reference.

You need reusable persona artifacts from research for docs, steering, and presentations – with optional visual outputs.

You need a fast UI prototype.

You need a prototype aligned to a client brand.

You need design critique before implementation.

You need a structured UX assessment with prioritized findings.

You need a comprehensive style guide from brand inputs.

You need interface copy for product experiences – button labels, error messages, onboarding flows, empty states.

You need a structured WCAG 2.2 accessibility audit with severity-scored findings.

You need annotated design handoff documentation for engineering.

You need a design system component specification with variants, states, and accessibility.

You need to synthesize usability test sessions into actionable findings.

You need a competitive UX heuristic walkthrough.

You need to facilitate a structured design critique session.

You need to plan and facilitate a design sprint.

You need to catalog and specify interaction patterns for consistency.

You need to audit a design system for coverage, consistency, and completeness.

You need a comprehensive brand book codifying visual identity, voice, and application rules.

You need to build design foundations from personas through prototyping to review.

You need to build or audit a design system from tokens through components to accessibility.

You need to validate designs through usability testing and polished handoff.

You need facilitation support for iteration planning sessions.

You need a timed script for any workshop or meeting.

You need a narrative and run-of-show for demo.

You are preparing a retrospective structure and script.

You need to turn retro output into concrete actions.

You need to prepare for and navigate a team conflict.

You need to categorize demo feedback into backlog actions.

You need to reframe raw feedback into underlying problems and outcomes.

You need to facilitate a retrospective session.

You need to help a team identify what is stuck and find the right intervention.

You need to run the full cycle of iteration ceremonies from IPM through demo and retro.

You need a structured naming process for a product, feature, or initiative with scoring criteria.

You need structured notes during or after standup capturing changes, blockers, and commitments.

You need the four daily PM skills chained together: wrapup, standup prep, facilitation, client summary.

You want an individual AI maturity assessment.

You need an organization-level AI maturity profile.

You need a structural health check of an AI system.

The team is stuck and needs a root-cause diagnostic.

You need to evaluate whether an initiative is a 10% optimization or a 10x trajectory change.

You need to evaluate AI adoption readiness and progress.

You need to facilitate an annual strategy review.

You need to identify cognitive biases in decisions or documents.

You need to synthesize insights across multiple engagements.

You need to score options against a chosen framework.

You need to extract recurring patterns from engagement data.

You need to assess product-led growth readiness.

You need to assess product operations maturity.

You need to facilitate role clarity discussions within a team.

You need to map security controls to compliance framework requirements with gap analysis and audit prep.

You need to assess a vendor's security posture before procurement or during periodic review.

You need to score and compare 2-4 technology vendors with a weighted criteria scorecard.

You need to choose and implement the right marketing attribution model.

You need to evaluate brand health across identity, perception, and consistency.

You need a structured analysis of campaign performance with actionable next steps.

You need to evaluate pages for conversion optimization opportunities.

You need to mine accumulated feedback and corrections to surface actionable patterns.

You need continuous improvement through external signal scanning and internal feedback analysis.

You need a health check on a product ops function – maturity, value, and role overlaps.

You need to evaluate social presence, performance, and competitive position.

You need to identify and prioritize assumptions before committing to a direction.

You need to plan a card sort to understand how users organize content.

You need to benchmark UX quality across competitors with task-flow analysis.

You need to validate a concept with users before building it.

You need to plan a diary study to understand behavior over time.

You need to prioritize research questions into a focused roadmap.

You need to present research findings to stakeholders.

You need to structure a research insight repository for reusable findings.

You need to design participant screening for research recruitment.

You need to design a survey with question design and analysis plan.

You need to plan a usability test from objectives to moderator guide.

You need to design discovery questions, build the script, and debrief findings.

You need to turn research questions into stakeholder-ready findings.

You need to feed user insights into planning through structured interviews and synthesis.