skills.rest
WayneWalterBerry
WayneWalterBerryCOMMUNITY
Explore all skills by this author →
GitHub

work-down-issues

Automate GitHub issue burndown with parallel wave planning and final verification gates.

Updated Mar 19, 2026
Search Tags:#planning#github#parallel#backlog#issue-tracking#waves#burndown
One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill work-down-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-down-issues
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.squad/skills/work-down-issues
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill work-down-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to aggressively close open GitHub issues by planning parallel waves of work, ensuring efficient backlog reduction and gating with a final test pass.

Core Features & Use Cases

  • Burndown planning: break the backlog into waves to maximize parallel work while respecting dependencies.
  • Owner routing: assign issues to agents based on labels and expertise to accelerate resolution.
  • Verification gate: require Marge-like verification and a test-pass before closing the cycle, ensuring quality.

Quick Start

Initiate Wave 1 immediately and report the results, then proceed with subsequent waves until all issues are closed.

Frequently Asked Questions about work-down-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub backlog burndown for issues with dependencies?▼

Automating GitHub backlog burndown involves planning parallel work waves that respect issue dependencies, routing issues to owners, and gating closure with a final test pass.

What is dependency-aware wave planning for issue tracking?▼

Dependency-aware wave planning is breaking a backlog into parallel work batches that maximize throughput while strictly respecting GitHub issue dependencies to safely reduce open counts.

How do I close multiple GitHub issues in parallel without breaking dependencies?▼

You can close multiple GitHub issues in parallel by scheduling dependency-aware work waves, routing issues by label, and enforcing a TDD-style verification gate before final closure.

Can I use automated owner routing for large GitHub repositories?▼

Yes, automated owner routing assigns open GitHub issues to agents based on labels and expertise, accelerating backlog resolution within large repositories during parallel wave execution.

What is the best way to verify GitHub issue closure in an automated burndown?▼

The best way to verify automated GitHub issue closure is applying a Marge-like verification gate requiring a final test-pass and automated commit logging before the burndown cycle completes.

Related Skills

Explore More Product & Management Skills→
decebalsdecebals
700

issue-triage

Categorize GitHub issues by type and priority for Java projects.

Community
Intermediate
dmlguq456dmlguq456
7

execute-plan

Execute plans end-to-end with structured progress tracking and auditable logs.

Community
Advanced
Rwb3nRwb3n
1

dod-validation-cycle

Validate Definition of Done criteria before work-item closure.

Community
Advanced
cdubiel08cdubiel08
2

ralph-triage

Automates GitHub issue triage by validating, closing duplicates, splitting, and routing them.

Community
Advanced