Saltar al contenido
Marketplace

wwas

de phuryn

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.

Resumen

SKILL.mdLeída en 8607e3b

Why-What-Acceptance (WWA)

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 context

Step-by-Step Process

  1. Define the strategic Why - Connect work to business and team objectives
  2. Describe the What - Keep descriptions concise, reference designs
  3. Write Acceptance Criteria - High-level, not detailed specifications
  4. Ensure independence - Items can be developed in any order
  5. Keep items negotiable - Invite team conversation, not constraints
  6. Make items valuable - Each delivers measurable user or business value
  7. Ensure testability - Outcomes are observable and verifiable
  8. Size appropriately - Small enough for one sprint estimate

Item Template

Title: [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:

  • [Observable outcome 1]
  • [Observable outcome 2]
  • [Observable outcome 3]
  • [Observable outcome 4]

Example WWA Item

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:

  • Spending totals update within 2 seconds of logging an expense
  • Budget progress is visually indicated with a progress bar
  • Users can see remaining budget amount at a glance
  • System handles multiple expense categories correctly

Output Deliverables

  • Complete set of backlog items for the feature
  • Each item includes Why, What, and Acceptance Criteria sections
  • Items are independent and deliverable in any order
  • Items are sized for estimation and completion in one sprint
  • Strategic context is clear for team decision-making
  • Design references are included for implementation guidance

Further Reading

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add phuryn/pm-skills --skill wwas

Más de phuryn

  • create-prdphurynCreate a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.10.4 k instalaciones en skills.sh0
  • competitor-analysisphurynAnalyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.3,600 instalaciones en skills.sh0
  • business-modelphurynGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.3,500 instalaciones en skills.sh0
  • privacy-policyphurynDraft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.3,200 instalaciones en skills.sh0
  • brainstorm-ideas-newphurynBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.3,100 instalaciones en skills.sh0
Todas las skills de phuryn