What it is
to-issues breaks a plan, spec, or PRD into independently grabbable issues. Its source guidance emphasizes tracer-bullet vertical slices rather than giant task lists.
Why it is useful
Agents work better when tasks are small, scoped, and reviewable. This skill helps convert planning output into tickets that can be assigned, verified, and shipped separately.
Best uses
- Split a PRD into implementation issues.
- Prepare work for multiple agents or developers.
- Convert a broad refactor into safe vertical steps.
Notes
Good issue slicing still needs dependency awareness. Keep shared migrations, release sequencing, and risky data changes explicit.