gg-plan-backlog

Automate backlog grooming by turning rough notes into a structured, worker-ready backlog through epic breakdown, dependency wiring, and sprint-wave output. It orchestrates analysis and prompt preparation to generate organized work items for an upcoming sprint.

The best way to break down epics is to decompose large initiatives into actionable tasks and work units, then wire dependencies and assign quality gates. This creates coherent waves of prioritized work ready for sprint execution.

Dependency wiring connects tasks within decomposed epics by setting priorities from 0 to 4 and linking related work units. This ensures coherent sprint waves where blocked tasks are properly sequenced before work proceeds.

Yes, you can generate worker-ready prompts for each backlog item using Haiku. The skill prepares issue prompts by running prompt-writing commands, ensuring every task has clear descriptions and owners before sprint execution.

Yes, you need MCP Beads to inspect backlog health and readiness, create epics and subtasks, and wire dependencies. The skill uses specific MCP Beads commands to assess blockers and present organized waves of work for spawning.

Automated sprint planning requires rough notes as input and depends on MCP Beads and Haiku prompts to function. It cannot generate work items without initial notes, and quality gates must be manually assigned to ensure quality before work proceeds.