Turn feature ideas into backlog items, a team's planned units of work, using Why, What, and Acceptance Criteria. Connect each item to business goals and define observable outcomes in independent pieces sized for one sprint.
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
Review the instructions the agent will receive before you install.
Create product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.
Use when: Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.
Arguments:
$PRODUCT: The product or system name$FEATURE: The new feature or capability$DESIGN: Link to design files (Figma, Miro, etc.)$ASSUMPTIONS: Key assumptions and strategic contextTitle: [What will be delivered]
Why: [1-2 sentences connecting to strategic context and team objectives]
What: [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]
Acceptance Criteria:
Title: Implement Real-Time Spending Tracker
Why: Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.
What: Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.
Acceptance Criteria:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.
Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.
Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.
Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.
Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.
Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.