Skip to content
SkillModel-led591 tokens in use

wwas

Write product backlog items in Why-What-Acceptance format with strategic context, a short description and observable criteria.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/wwas
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing wwas costs

48tokens idle
591tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure22/25
  • Examples3/15
  • Output5/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

wwas produces backlog items in the Why-What-Acceptance format. Each item has a title, a Why that ties the work to strategy and team objectives, a What that is a short description with a design link, and acceptance criteria written as observable outcomes.

Items are meant to be independent, negotiable, valuable, testable and small enough for one sprint estimate, and the What is a reminder of a team discussion, not a detailed specification.

What You Get

  • A set of backlog items for the feature
  • A Why section with strategic context for each
  • A What section of one or two paragraphs with the design link
  • High-level, observable acceptance criteria
  • Items that can be built in any order and fit one sprint

Common Use Cases

  • Communicating strategic intent to a team through backlog items
  • Splitting a feature into independent work items
  • Writing items that invite conversation

What Makes It Unique

The Why comes first, so every item carries its strategic reason, and the What is kept short on purpose so detailed specifications emerge from conversation. Acceptance criteria stay high-level.

Under The Hood

The skill is one SKILL.md of instructions with no scripts. It takes the product, feature, design link and assumptions as arguments and writes the items in its reply. The design link is placed in the item text and is not fetched.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers