borghei/Claude-Skills / project-management/execution/wwas
wwas
VerifiedWrites and grades Why-What-Acceptance backlog items so each one traces to an OKR and passes INVEST before a sprint. Use when writing backlog items, checking sprint readiness, or finding work that serves no objective.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.4 KB |
| assets/sample_backlog.json | config | 2.2 KB |
| assets/sample_backlog_ready.json | config | 2.0 KB |
| assets/wwas_template.md | markdown | 3.3 KB |
| examples/northwind-backlog-rewritten.md | markdown | 11.3 KB |
| references/backlog-management-guide.md | markdown | 9.2 KB |
| references/red-flags.md | markdown | 10.6 KB |
| references/wwas-format-and-examples.md | markdown | 10.0 KB |
| scripts/backlog_alignment_checker.py | script | 8.8 KB |
| scripts/invest_gate_checker.py | script | 9.2 KB |
| scripts/wwas_quality_scorer.py | script | 9.4 KB |
assets/wwas_template.md
View on GitHub# WWAS Templates
## Single WWAS Backlog Item
### [Title -- Short, Descriptive Name]
**Why:**
[1-2 sentences connecting to a strategic objective, OKR, or business goal. Explain why this matters and why now.]
**What:**
[1-2 paragraphs describing the change. This is a reminder of the discussion, not a detailed specification. The team should read this and recall what was agreed.]
[Design: link to Figma / Sketch / wireframe, or "TBD"]
**Acceptance Criteria:**
1. [ ] [Observable outcome that defines done]
2. [ ] [Observable outcome under a specific condition]
3. [ ] [Edge case or error state handling]
4. [ ] [Performance, accessibility, or cross-platform criterion]
**INVEST Check:**
| Criterion | Pass? | Notes |
|-----------|-------|-------|
| Independent | [ ] | No blocking dependencies |
| Negotiable | [ ] | Implementation open to discussion |
| Valuable | [ ] | Clear user or business value |
| Estimable | [ ] | Team can size this confidently |
| Small | [ ] | Fits within one sprint |
| Testable | [ ] | Acceptance criteria are verifiable |
**Estimate:** [Story points or T-shirt size]
**Priority:** [P0 / P1 / P2 / P3]
**Sprint:** [Target sprint or "Backlog"]
---
## Batch WWAS Template
Use this table to draft multiple items quickly, then expand the highest-priority items into full cards.
| # | Title | Why (objective connection) | What (brief description) | AC Count | Estimate | Priority |
|---|-------|--------------------------|--------------------------|----------|----------|----------|
| 1 | | | | | | |
| 2 | | | | | | |
| 3 | | | | | | |
| 4 | | | | | | |
| 5 | | | | | | |
| 6 | | | | | | |
| 7 | | | | | | |
| 8 | | | | | | |
### Batch Review Checklist
- [ ] Every item has a Why that references a specific objective or metric
- [ ] No item's What reads like a specification (1-2 paragraphs max)
- [ ] Each item has 4+ acceptance criteria
- [ ] All items pass INVEST (especially Independent and Small)
- [ ] Items are ordered by priority
- [ ] Design links are included where applicable
---
## Refinement Session Template
Use this template to structure a backlog refinement session around WWAS items.
### Refinement Session -- [Date]
**Attendees:** [Names and roles]
**Duration:** [Time] minutes
**Items to Refine:** [Number]
#### Pre-Refinement Preparation
- [ ] Items shared with the team 24 hours in advance
- [ ] Design artifacts linked and accessible
- [ ] Previous refinement action items reviewed
#### Agenda
| Time | Activity |
|------|----------|
| 5 min | Review action items from last refinement |
| 5 min per item | Walk through each item: Why, What, Acceptance Criteria |
| 5 min | Estimate refined items |
| 5 min | Identify items needing spikes or follow-up |
#### Item-by-Item Notes
**Item: [Title]**
- Why discussion: [Notes on strategic alignment -- did the team agree?]
- What discussion: [Notes on scope -- any changes to the description?]
- AC discussion: [Notes on acceptance criteria -- additions, removals, changes?]
- Estimate: [Story points or T-shirt size]
- Status: Ready / Needs spike / Needs design / Needs follow-up
- Follow-up: [Any actions needed before this is sprint-ready]
*(Repeat for each item)*
#### Session Outcomes
- Items refined: [Count]
- Items ready for sprint: [Count]
- Items needing follow-up: [Count]
- Spikes identified: [List]
- Next refinement: [Date]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |