📋
Writing

Why What Acceptance

by phuryn

Why What Acceptance is a Writing skill for Claude Code, published by phuryn in pm-skills.

25.2K stars2.7K forkson phuryn/pm-skillsAdded 2026/08/14Repository updated 2026/07/03
agent-skill-repositoryagent-skillsagentic-skillsclaude-code-marketplaceclaude-code-pluginsclaude-cowork-pluginproduct-management
Install in seconds
Install Why What Acceptance
Copy Why What Acceptance into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas ~/.claude/skills/wwas

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/phuryn/pm-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
pm-execution/skills/wwas/SKILL.md in phuryn/pm-skills
Installs to
~/.claude/skills/wwas
Collection
One of 25 skills cataloged from this repository
Category
Writing1012 skills

What Why What Acceptance does

Why What Acceptance creates product backlog items in Why-What-Acceptance format, producing independent, valuable, testable items with strategic context. Use it when writing structured backlog items, breaking features into work items, or communicating strategic intent to teams.

Why What Acceptance is cataloged under Writing on DirSkills. Why What Acceptance comes from a repository tagged agent-skill-repository, agent-skills, agentic-skills, claude-code-marketplace and claude-code-plugins.

Documentation

README

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Why What Acceptance

  • What else does phuryn publish alongside Why What Acceptance?

    Why What Acceptance is one of 25 skills that DirSkills catalogs from phuryn/pm-skills, the repository it ships in. Its siblings there include A/B Test Analysis, Beachhead Segment and Brainstorm Team OKRs. Each one is a separate skill with its own page in this directory, installs the same way Why What Acceptance does, and is maintained by phuryn in that same repository. The rest of the collection is listed on the phuryn/pm-skills page.

  • How does Why What Acceptance compare to other Writing skills?

    Why What Acceptance ranks #52 by stars among the 1012 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Why What Acceptance against them. Open each page to compare what they document and how they install.

More from phuryn/pm-skills

Why What Acceptance is one of 25 skills cataloged on DirSkills from phuryn/pm-skills.

See all 25 skills
📊
2w ago

A/B Test Analysis

A/B Test Analysis evaluates A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when interpreting split test data, checking if a test reached significance, or deciding whether to ship a variant.
Data
25.2K2.7K
🎯
2w ago

Beachhead Segment

Beachhead Segment identifies the first beachhead market segment for a product launch by evaluating segments against burning pain, willingness to pay, winnable market share, and referral potential. Use it when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Data
25.2K2.7K
🎯
2w ago

Brainstorm Team OKRs

Brainstorm Team OKRs generates three alternative OKR sets aligned with company strategy, each with a qualitative objective and three measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Writing
25.2K2.7K
📊
2w ago

Cohort Analysis

Cohort Analysis helps analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement. Use it when studying retention curves, feature adoption over time, churn patterns, or engagement trends.
Data
25.2K2.7K
⚔️
2w ago

Competitive Battlecard

Competitive Battlecard creates sales-ready battlecards comparing your product against a specific competitor, including positioning, feature comparison, objection handling, and win/loss patterns. Use it when preparing sales teams, creating competitive materials, or answering 'why not competitor X?'
Writing
25.2K2.7K
📝
2w ago

Create PRD

Create PRD guides an agent through writing a Product Requirements Document using an 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use it when drafting a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Writing
25.2K2.7K