to-issues

Convert plans or PRDs into dependency-ordered issue bodies for tracker publication.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill to-issues-matt-riley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/to-issues
Command: npx skills add https://github.com/matt-riley/agent-skills --skill to-issues-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Turn high-level plans, specs, PRDs, or approved ideas into independent, tracker-ready issue slices that can be delivered incrementally.

Core Features & Use Cases

  • Breaks existing work into thin, vertical slices that can be tracked as individual issues with explicit dependencies.
  • Produces ready-to-paste issue bodies and an ordered publication plan to publish in dependency order.
  • Guides teams on when to use this approach and when to route to alternative skills if broader framing is still needed.

Quick Start

Draft the first vertical-slice breakdown from the provided source material and present it for approval before publishing.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I break a PRD into trackable issues for a project tracker?▼

To break a PRD into trackable issues, the Skill transforms approved plans into thin, vertical-slice tickets with explicit dependencies. It outputs ready-to-paste issue bodies and an ordered publication plan for your tracker.

What are vertical slices in issue tracking and when do I need them?▼

Vertical slices in issue tracking are end-to-end, demoable ticket segments of a larger plan. You need them when breaking approved work into independently grabbable pieces that can be delivered and tracked incrementally.

How do I create an ordered publication plan for issue dependencies?▼

You create an ordered publication plan by breaking source material into tracer-bullet slices with explicit dependencies. The Skill automatically generates the ordered sequence for publishing these ready-to-paste issues to your tracker.

Do I need acceptance criteria and an epic context before slicing work into issues?▼

Yes, you need clear source material, acceptance criteria, and an epic context before slicing work. The Skill requires these prerequisites to produce independently grabbable, tracker-ready vertical-slice tickets for publication.

When should I not use vertical-slice issue breakdown for product management?▼

You should avoid vertical-slice issue breakdown when broader framing or initial planning is still needed. If the high-level plan, spec, or PRD lacks approved ideas and clear acceptance criteria, route to alternative skills for framing first.

What's the best way to turn approved plans into demoable tickets?▼

The best way to turn approved plans into demoable tickets is drafting a vertical-slice breakdown from source material, presenting it for approval, then pasting the generated issue bodies into your tracker in dependency order.