title: Write a User Story

description: Capture a requirement as a clear user story with acceptance criteria.

content:
Turn this requirement into a user story: {{requirement}}

Format: 'As a [user], I want [capability], so that [benefit].' Then write acceptance criteria as concrete, testable Given/When/Then statements covering the happy path and the important edge cases. Keep it focused on user-observable behavior, not implementation. Flag any ambiguity that needs a product decision before this is ready to build.

requirement

description: The raw requirement


title: Write a PRD

description: Draft a crisp product requirements document.

content:
Write a PRD for: {{feature}}

Include: the problem and who has it, the goal and success metrics, what's in and explicitly out of scope, the core user flows, and the open questions. Keep it decision-oriented — every section should help someone build or prioritize. Avoid solutioning the implementation. End with the riskiest assumption that, if wrong, sinks the feature.

feature

description: The feature to spec


title: Prioritize a Backlog

description: Rank competing work by value and cost transparently.

content:
Help me prioritize these items: {{items}}

Given my goal: {{goal}}

For each, estimate value (impact on the goal) and cost (effort/risk), then rank them. Surface dependencies and any quick wins. Be explicit about the trade-off you're making and what you're deprioritizing. Recommend what to do next sprint and what to consciously NOT do.

items

description: The backlog items

goal

description: The current objective


title: Define Success Metrics

description: Choose metrics that prove a feature worked.

content:
For this feature/initiative: {{feature}}

Define how we'll know it succeeded. Propose a primary success metric tied to the user/business outcome (not just usage), supporting metrics, and a guardrail metric to catch harm. For each, give the precise definition and a target or direction. Avoid vanity metrics. Tell me what we'd conclude if the primary metric moves but the guardrail breaks.

feature

description: The feature or initiative


title: Critique a Feature Idea

description: Stress-test a product idea before committing to it.

content:
Here's a feature idea: {{idea}}

Play skeptical PM. Ask: what user problem does this actually solve, and how do we know it's real? Who's it for, and is that a big enough group? What's the simplest version that would validate it? What are we NOT building if we build this? What would make this fail? End with: is this worth a cheap experiment, a full build, or a pass — and why.

idea

description: The feature idea


title: Plan an MVP

description: Scope the smallest version that tests the core bet.

content:
I want to build: {{product}}

Help me scope an MVP. What's the core hypothesis we're testing? What's the absolute minimum that tests it honestly with real users? Ruthlessly cut everything that isn't essential to that test, and list what we're deferring. Define what result would tell us to double down vs. pivot vs. kill. Resist gold-plating.

product

description: What you want to build


title: Run a Pre-Mortem

description: Imagine the project failed and work backward to prevent it.

content:
We're about to start: {{project}}

Run a pre-mortem. Imagine it's six months from now and this failed badly. Brainstorm the plausible reasons why — technical, product, team, market, and execution. Rank them by likelihood and impact. For the top risks, propose a concrete action we can take NOW to reduce or detect them early. Be specific, not generic.

project

description: The project you're starting


title: Turn Feedback into Action

description: Convert raw user feedback into prioritized product changes.

content:
Here's user feedback I collected: {{feedback}}

Synthesize it: group the feedback into themes, separate what users SAID from the underlying problem they have, and distinguish loud-but-rare from quiet-but-common. For the top themes, propose a concrete product response and how to validate it's the right one. Flag any feedback that's a vocal-minority trap we shouldn't chase.

feedback

description: The raw user feedback


title: Write a Problem Statement

description: Sharpen a vague problem before proposing solutions.

content:
Here's the problem I think we have: {{problem}}

Sharpen it into a crisp problem statement before anyone jumps to solutions. Pin down: who has the problem, when and how often it bites, what they do today, and what the cost of it is. Separate the symptom from the root problem. Flag where I've smuggled a solution into the problem framing. End with the one question whose answer would most change our approach.

problem

description: The problem as you see it


title: Prioritize with RICE

description: Rank competing initiatives objectively.

content:
Help me prioritize these initiatives: {{initiatives}}

Apply RICE (Reach, Impact, Confidence, Effort). For each, reason out each factor and where the estimate is shaky, then compute the score. Show the ranking, but treat it as a conversation starter, not gospel: call out where a low-confidence guess is driving the order, and which item you'd validate before committing. Note anything strategic that RICE structurally undervalues.

initiatives

description: The initiatives to rank


title: Decide Build vs Buy

description: Reason through building something yourself versus adopting it.

content:
I'm deciding whether to build or buy: {{capability}}

Reason it through honestly. Cover the total cost of building (not just v1, but maintenance, edge cases, and opportunity cost) versus buying (price, lock-in, fit, and the gaps you'll still have to fill). Decide whether this is core to us — something we should own — or undifferentiated plumbing better bought. Name the hidden cost each side conveniently ignores, and recommend one with the condition that would flip it.

capability

description: The capability in question


title: Write a User Story with Acceptance Criteria

description: Turn a feature idea into a buildable, testable story.

content:
Turn this into a user story: {{feature}}

Write it as: as a [user], I want [capability], so that [outcome] — with the outcome being a real benefit, not a restatement of the capability. Then write acceptance criteria in given/when/then form that are specific and testable, covering the happy path, the key edge cases, and what's explicitly out of scope. Flag any criterion that's actually ambiguous about who decides done.

feature

description: The feature idea


title: Write a Competitive Analysis

description: Size up alternatives honestly to find your angle.

content:
Analyze the competitive landscape for: {{product}}

Map the real alternatives — including do-nothing and homegrown, not just direct competitors. For each, what they do well, where they fall short, and who they serve. Find the gap or angle we can credibly own, and be honest about where they beat us. Avoid the trap of listing features; focus on the job the user is hiring a product to do. End with the one differentiator worth betting on.

product

description: Your product or idea


title: Define a Target Persona

description: Sharpen who you are building for.

content:
Help me define the target user for: {{product}}

Get specific: their context, the job they are trying to get done, what they do today, and what frustrates them. Separate the person who uses it from the one who buys it if they differ. Avoid a demographic caricature — anchor on goals and behavior. State who we are explicitly NOT for, because trying to serve everyone serves no one. End with the one insight about this user that should shape the product.

description: The product


title: Plan a Product Launch

description: Sequence the work to ship and land a launch.

content:
Help me plan the launch of: {{feature}}

Work backward from the goal. Define what success looks like and how it is measured. Sequence the work: readiness (the thing actually works and is supportable), the rollout (flag, gradual, or big bang) matched to the risk, and the announcement and enablement. Identify the riskiest assumption to de-risk before launch. List what could go wrong on launch day and the plan for each. Keep it honest about what is must-have versus nice-to-have.

feature

description: What you are launching


title: Map a User Journey

description: Trace the end-to-end experience to find friction.

content:
Map the user journey for: {{scenario}}

Walk through it stage by stage from the user's first trigger to their goal (and beyond, to retention). At each step capture what they do, what they think and feel, and where they get stuck or drop off. Find the highest-friction moment — the one that loses the most users — and the moment of delight worth amplifying. Distinguish problems worth fixing from minor annoyances. End with the single highest-leverage improvement.

scenario

description: The journey to map