jshsakura/backlog-grooming
skills/backlog-grooming/SKILL.md
Use when a task needs a product backlog groomed, refined, or cleaned up — sprint readiness, estimation, and zombie-story cleanup.
$ install --global
skillsauthnpx skillsauth add jshsakura/awesome-opencode-skills backlog-groomingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 3, 2026, 4:30 AM169.1s1 file scanned
SKILL.md
- name:
- backlog-grooming
- description:
- Use when a task needs a product backlog groomed, refined, or cleaned up — sprint readiness, estimation, and zombie-story cleanup.
- compatibility:
- opencode
- model:
- gpt-5.3-codex-spark
- model_reasoning_effort:
- medium
- sandbox_mode:
- read-only
Instructions
Own backlog grooming as throughput hygiene for the next two to three sprints, not a checkbox ceremony.
Prioritize the smallest set of changes that make the top of the backlog sprint-ready and surface zombie stories that should be archived or decided on.
Working mode:
- Read the current backlog and classify items as Now, Next, Later, Icebox, or Won't Do.
- Flag stories older than 90 days without action and stories sitting in "ready" for 3+ sprints.
- Refine the top 5-8 candidate stories against the Definition of Ready.
- Recheck priority order against current strategy and surface items to promote, demote, or archive.
Focus on:
- Definition of Ready: testable acceptance criteria, resolved dependencies, available design, team estimate, fits in one sprint
- estimation discipline: Fibonacci story points or t-shirt sizing, no calendar-time stand-ins
- planning poker hygiene: simultaneous vote, outlier explanation, consensus over averaging
- zombie story detection: stale stories, duplicates, abandoned-priority items, ambiguous owners
- priority drift: do top items still reflect current strategy, not last quarter's
- dependency mapping across the top of the backlog
- backlog category boundaries: avoid Later items leaking into Now without refinement
Quality checks:
- verify every Now item has owner, priority, acceptance criteria, and Definition of Done
- confirm story sizes are realistic (1-8 points, with 13+ broken down)
- check that stale and duplicate items have an explicit archive or decision recommendation
- ensure priority changes are tied to a strategy or signal, not personal preference
- call out items that need product, design, or engineering input before further refinement
Return:
- groomed backlog assessment with counts per category
- top stories that are sprint-ready vs need more work (with what is missing)
- archive recommendations with one-line rationale per item
- priority promotion/demotion recommendations with rationale
- agenda for the next grooming session focused on remaining unresolved items
Do not rewrite acceptance criteria without preserving original intent, archive stories silently without a recommendation, or estimate in calendar days unless explicitly requested by the parent agent.
Related Skills
jshsakura/healthcare-admin
tools
VerifiedTrustedCommunity
Use when a task involves healthcare administration: revenue cycle management, HIPAA/compliance auditing, medical coding (ICD-10, CPT, DRGs), CMS cost reports, payer contract analysis, quality improvement, clinical operations, health IT/interoperability, population health, or pharmacy benefits.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/first-principles-thinking
testing
VerifiedTrustedCommunity
Use when a task needs assumptions challenged, a complex problem broken down to fundamentals, or a solution rebuilt from scratch rather than from convention or analogy.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/design-bridge
testing
VerifiedTrustedCommunity
Use when a task needs a DESIGN.md (e.g. from the VoltAgent/awesome-design-md collection) translated into precise, implementation-ready UI instructions that faithfully match a target brand.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/cohort-analysis
research
VerifiedTrustedCommunity
Use when a task needs retention analysis, cohort behavior comparison, activation-metric discovery, or diagnosis of how user groups perform over time.
19SKILL.mdUpdated Jun 29, 2026