Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Why-What-Acceptance backlog format that connects every work item to strategic business objectives, with INVEST quality gates and observable acceptance criteria.
Install Wwas
$ npx skills add borghei/Claude-Skills --skill wwas -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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 borghei/Claude-Skills --skill wwas -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills wwas --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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 borghei/Claude-Skills --skill wwas -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills wwas --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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/borghei/Claude-Skills.git --path project-management/execution/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 borghei/Claude-Skills --skill wwas -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills wwas --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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 borghei/Claude-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 borghei/Claude-Skills --skill wwas -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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 borghei/Claude-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 borghei/Claude-Skills wwas --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/execution/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/borghei/Claude-Skills/tree/main/project-management/execution/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
- 881
- Token cost
- ~1.4k tokens
- SKILL.md length
- 653 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Why-What-Acceptance backlog format that connects every work item to strategic business objectives, with INVEST quality gates and observable acceptance criteria.
- Tasks that involve User stories
- SKILL.md covers Overview, Clarify First, References and Integration with Other Skills, plus 2 more sections
- Runs Python scripts from its folder
- Tasks that involve Quality gates
What it does
Wwas is an agent skill from borghei/Claude-Skills. Why-What-Acceptance backlog format that connects every work item to strategic business objectives, with INVEST quality gates and observable acceptance criteria.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `assets/wwas_template.md`, `examples/northwind-backlog-rewritten.md` and `references/backlog-management-guide.md`).
It sits in Product & Project Management, covering User stories and Quality gates. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Tasks that involve User stories
- Tasks that involve Quality gates
Example prompts
- “/wwas”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. 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
Ships 3 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 1.4k tokens when it runs, and up to ~9k if it reads all its reference files. Until then it costs about 41 tokens; SKILL.md has 653 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); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 653 words, ~1,426 tokens.
Download SKILL.mdSave it as
.claude/skills/wwas/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- wwas
- description
- Why-What-Acceptance backlog format that connects every work item to strategic business objectives, with INVEST quality gates and observable acceptance criteria.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.1
- metadata.author
- borghei
- metadata.category
- project-management
- metadata.domain
- pm-execution
- metadata.updated
- 2026-06-15
- metadata.tech-stack
- backlog-management, invest-criteria, strategic-alignment
Why-What-Acceptance Backlog Expert
Overview
Create backlog items using the Why-What-Acceptance (WWAS) format. This format ensures every piece of work connects to strategic context, includes a concise description that serves as a "reminder of the discussion" rather than a detailed specification, and defines high-level acceptance criteria focused on observable outcomes.
The format has three parts:
- Why (1-2 sentences): connects the item to a business objective, OKR, or theme; answers "why does this matter?" and "why now?" If you cannot write a compelling Why, the item should not be prioritized.
- What (1-2 paragraphs): a reminder of the refinement discussion, not a specification. Link the design if one exists.
- Acceptance Criteria (4+): observable outcomes that define done — not implementation steps or test scripts.
Before an item enters a sprint, it must pass the INVEST gates (Independent, Negotiable, Valuable, Estimable, Small, Testable).
When to Use
- Backlog creation -- building a product backlog where strategic alignment is critical.
- Sprint planning -- refining items and the team needs to understand why each matters.
- Stakeholder communication -- executives need to see how work connects to business objectives.
- Roadmap decomposition -- breaking roadmap themes into actionable backlog items.
When NOT to Use
- When you need situation-driven requirements -- use
job-stories/instead. - A pure technical task with no strategic context (use a simple task description).
- The team prefers traditional user stories and strategic context is well-understood.
Clarify First
Before writing the item, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- The strategic objective / OKR it connects to — drives the Why; without it the Why is a forced exercise and the item should not be prioritized
- The refinement discussion or design link — becomes the What (a reminder of the discussion, not a specification)
- The observable done-state — drives the Acceptance Criteria (outcomes a user or system can observe, not implementation steps or test scripts)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
References
Load the reference that matches the task; keep this file lean and pull detail on demand.
- references/wwas-format-and-examples.md — full Why/What/Acceptance writing rules with good/bad examples, the INVEST gate table, the item template, a complete worked example, the objective-mapping table, troubleshooting, and success criteria. Read this when writing or reviewing actual WWAS items.
- references/backlog-management-guide.md — format comparison (WWAS vs user stories vs job stories), INVEST deep dive, Definition of Ready, and refinement best practices. Read when choosing a format or running refinement.
- references/red-flags.md — bad-vs-good quoted examples of WWAS items. Scan every item before it enters refinement.
assets/wwas_template.md— ready-to-use WWAS templates.
Show full SKILL.md (223 more words)Show less
Integration with Other Skills
- Use
job-stories/for situation-driven stories focused on user context rather than strategic alignment. - Use
brainstorm-okrs/to define the objectives that WWAS items connect to. - Use
summarize-meeting/to capture refinement discussions that inform the What. - Feed WWAS items into
../jira-expert/for ticket creation with structured fields.
Scope & Limitations
In Scope: Writing items in WWAS format, applying INVEST gates, connecting work to strategic objectives, facilitating refinement, converting existing items to WWAS, integrating with Jira.
Out of Scope: Situation-driven requirements (job-stories/), ideation/discovery (discovery/brainstorm-ideas/), OKR definition (execution/brainstorm-okrs/), detailed technical specs, sprint planning/capacity (../scrum-master/).
Limitations: WWAS adds most value with clearly defined objectives (OKRs, North Star). Without strategic context the Why becomes a forced exercise. It fits product/feature work better than pure tech-debt/infra items. Teams transitioning from user stories may need 2-3 sprints to build fluency.
Integration Points
| Integration | Direction | What Flows |
|---|---|---|
job-stories/ | Complementary | Job stories add situational context (When); WWAS adds strategic context (Why). Use both for complete requirements |
summarize-meeting/ | Meetings -> WWAS | Refinement discussions produce the What; decisions produce acceptance criteria |
../jira-expert/ | WWAS -> Jira | WWAS items become Jira tickets with structured description fields |
execution/brainstorm-okrs/ | OKRs -> WWAS | Team OKRs provide the strategic objectives that Why statements reference |
execution/prioritization-frameworks/ | WWAS -> Prioritization | WWAS items scored via RICE or other frameworks for backlog ordering |
discovery/brainstorm-ideas/ | Ideas -> WWAS | Validated ideas decompose into WWAS backlog items with strategic traceability |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (scripts, references, assets) in project-management/execution/wwas of borghei/Claude-Skills.
- SKILL.md
- assets/wwas_template.md
- examples/northwind-backlog-rewritten.md
- references/backlog-management-guide.md
- references/red-flags.md
- references/wwas-format-and-examples.md
- scripts/backlog_alignment_checker.py
- scripts/invest_gate_checker.py
- scripts/wwas_quality_scorer.py
Open the folder on GitHubat commit 4a698e8
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 skillborghei/Claude-Skills | 881 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Sdd Authoringmagnus919/hermes-profiles | 281 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Verification Gatesrohitg00/skillkit | 1.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
Sdd Authoring
magnus919/hermes-profiles
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
Verification Gates
rohitg00/skillkit
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding.
Remediate Failures
digipulse-engineering/GAAI-framework
Correct failures, rule violations, and acceptance criteria gaps detected during QA review.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Wwas
What does Wwas do?
Why-What-Acceptance backlog format that connects every work item to strategic business objectives, with INVEST quality gates and observable acceptance criteria. Wwas is an agent skill from borghei/Claude-Skills. Why-What-Acceptance backlog format that connects every work item to strategic business objectives, with INVEST quality gates and observable acceptance criteria.
When should I use Wwas?
Wwas fits situations like: tasks that involve User stories; tasks that involve Quality gates.
How do I install Wwas in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill wwas -a claude-code`. Or copy the skill folder (project-management/execution/wwas in borghei/Claude-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 borghei/Claude-Skills --skill wwas -a codex`. Or copy the skill folder (project-management/execution/wwas in borghei/Claude-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 borghei/Claude-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?
Going by SKILL.md and its folder, Wwas needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Wwas access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Wwas use?
Wwas is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wwas use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.5k tokens, read only when the agent opens those files.
What are the alternatives to Wwas?
Skills that share tags, products or a category with Wwas: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and Sdd Authoring (magnus919/hermes-profiles, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wwas?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.