跳到正文
cccskills
免费在 GitHub 公开

wwas

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.

集成工具Figma
查看安装方法

适用场景

  • Breaking a feature into independent work items
  • Explaining the business purpose behind development work
  • Writing observable acceptance criteria
  • Preparing backlog items sized for one sprint

包含的文件(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示英语简介。

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7万2026年10月16日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7万2026年10月16日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7万2026年10月16日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7万2026年10月16日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7万2026年10月16日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7万2026年10月16日 更新

查看 phuryn 的全部技能

报告此技能的问题