ticket-breakdown

What problem does it solve?

This skill helps product teams and engineers convert vague feature requests into a structured, independent set of implementation issues that can be tackled in parallel, reducing delays and coordination overhead.

Core Features & Use Cases

• Creates an issues/ directory with a phased breakdown and explicit dependencies for each issue.
• Generates ISSUE-*.md files with WHAT/WHY and acceptance criteria for each task.
• Outlines an implementation order across phases, including parallelizable work and dependency DAG.

Quick Start

To begin, run brainstorming to outline major components, then generate the issues/ folder, write README.md with phases and dependencies, and create ISSUE-*.md files following the WHAT/WHY pattern. Then run rumdl to lint the markdown files.