User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context.
Install Wwas
$ npx skills add phuryn/pm-skills --skill wwas -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install phuryn/pm-skills wwas --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-execution/skills/wwas .claude/skills/wwas && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wwas" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas into .claude/skills/wwas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wwas", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwasType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add phuryn/pm-skills --skill wwas -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install phuryn/pm-skills wwas --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pm-execution/skills/wwas .agents/skills/wwas && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wwas" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas into .agents/skills/wwas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wwas", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill wwas -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install phuryn/pm-skills wwas --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pm-execution/skills/wwas .cursor/skills/wwas && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wwas" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas into .cursor/skills/wwas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wwas", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/phuryn/pm-skills.git --path pm-execution/skills/wwas--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add phuryn/pm-skills --skill wwas -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install phuryn/pm-skills wwas --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pm-execution/skills/wwas .gemini/skills/wwas && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wwas" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas into .gemini/skills/wwas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wwas", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install phuryn/pm-skills wwasInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add phuryn/pm-skills --skill wwas -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/pm-execution/skills/wwas .github/skills/wwas && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wwas" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas into .github/skills/wwas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wwas", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill wwas -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install phuryn/pm-skills wwas --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pm-execution/skills/wwas .opencode/skills/wwas && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wwas" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas into .opencode/skills/wwas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wwas", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wwas- GitHub stars
- 27k
- Token cost
- ~771 tokens
- SKILL.md length
- 362 words
- Files
- 1
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context.
- Works in 8 steps: Define the strategic Why - Connect work… → Describe the What - Keep descriptions… → Write Acceptance Criteria - High-level,… → …
- Writing structured backlog items
- SKILL.md covers Step-by-Step Process, Item Template, Example WWA Item and Output Deliverables
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wwas is an agent skill from phuryn/pm-skills. 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.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.
When your agent uses it
- Writing structured backlog items
- Breaking features into work items
- Using the WWA format
Example prompts
- “/wwas”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Define the strategic Why - Connect work to business and team objectives
- Describe the What - Keep descriptions concise, reference designs
- Write Acceptance Criteria - High-level, not detailed specifications
- Ensure independence - Items can be developed in any order
- Keep items negotiable - Invite team conversation, not constraints
- Make items valuable - Each delivers measurable user or business value
- Ensure testability - Outcomes are observable and verifiable
- Size appropriately - Small enough for one sprint estimate
What it can do on your machine
Read from SKILL.md and the folder at commit 8607e3b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
productcompass.pm
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wwas loads about 771 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 362 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from phuryn/pm-skills at commit 8607e3b, republished under its MIT licence (© phuryn). 362 words, ~771 tokens.
Download SKILL.mdSave it as
.claude/skills/wwas/SKILL.md (or your agent's skills folder).- name
- wwas
- description
- 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.
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
- Define the strategic Why - Connect work to business and team objectives
- Describe the What - Keep descriptions concise, reference designs
- Write Acceptance Criteria - High-level, not detailed specifications
- Ensure independence - Items can be developed in any order
- Keep items negotiable - Invite team conversation, not constraints
- Make items valuable - Each delivers measurable user or business value
- Ensure testability - Outcomes are observable and verifiable
- 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]
Show full SKILL.md (174 more words)Show less
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
© phuryn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in pm-execution/skills/wwas of phuryn/pm-skills.
Open the folder on GitHubat commit 8607e3b
Compare with similar skills
Wwas next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wwas this skillphuryn/pm-skills | 27k | — | ~771 | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 114 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
More from phuryn/pm-skills
All 67 skills in this repoAgreement-Based Code Review
phuryn/pm-skills
Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.
A/B Test Analysis
phuryn/pm-skills
Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.
Team OKR Brainstorm
phuryn/pm-skills
Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.
Cohort Analysis and Retention Explorer
phuryn/pm-skills
Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.
Dummy Dataset Generator
phuryn/pm-skills
Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.
Grammar and Flow Checker
phuryn/pm-skills
Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.
Related
Categories
Questions about Wwas
What does Wwas do?
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Wwas is an agent skill from phuryn/pm-skills. Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context.
When should I use Wwas?
Wwas fits situations like: writing structured backlog items; breaking features into work items; using the WWA format.
How do I install Wwas in Claude Code?
Run `npx skills add phuryn/pm-skills --skill wwas -a claude-code`. Or copy the skill folder (pm-execution/skills/wwas in phuryn/pm-skills) into .claude/skills/wwas in your project. Claude Code loads it when a task matches its description.
How do I install Wwas in Codex?
Run `npx skills add phuryn/pm-skills --skill wwas -a codex`. Or copy the skill folder (pm-execution/skills/wwas in phuryn/pm-skills) into .agents/skills/wwas in your project. Codex loads it when a task matches its description.
Can I use Wwas in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill wwas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wwas, .gemini/skills/wwas, .github/skills/wwas and .opencode/skills/wwas in your project.
What does Wwas need to run?
SKILL.md names no scripts, command-line tools or credentials: Wwas is instructions for the agent only.
Does Wwas access the network?
SKILL.md names 1 domain. As links in the text: productcompass.pm. This is read from the text; nothing was executed.
Is Wwas safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wwas use?
Wwas is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wwas use?
About 771 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wwas?
Skills that share tags, products or a category with Wwas: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wwas?
phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,845 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on September 14, 2026.
Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.