to-issues

Break down complex plans into independently-grabbable issues via vertical slicing.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/samuel-morrissey/skills --skill to-issues-samuel-morrissey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/samuel-morrissey/skills/tree/main/skills/to-issues
Command: npx skills add https://github.com/samuel-morrissey/skills --skill to-issues-samuel-morrissey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of converting complex plans, specifications, or PRDs into a series of actionable issues for project management.

Core Features & Use Cases

  • Vertical Slicing: Breaks down plans into independent, end-to-end issues.
  • User Interaction: Iterates with the user to refine the issue breakdown until approval.
  • Issue Tracking Integration: Publishes issues to the issue tracker with proper triage labels and dependencies.

Quick Start

Run the to-issues skill to initiate the issue breakdown process for your project plan.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I break down a complex project plan into manageable issues?

To break down a complex project plan into manageable issues, this Skill uses vertical slicing to split specifications into independent, end-to-end issues. It iterates with you to refine the issue breakdown until you approve the final list for project tracking.

What is vertical slicing in issue creation and how does it work?

Vertical slicing in issue creation divides a comprehensive plan into independently grabbable issues that cover end-to-end functionality. This ensures each issue delivers standalone value and maintains comprehensive coverage across the entire project management workflow.

Can I integrate plan breakdown directly with my issue tracking system?

Yes, you can integrate plan breakdown with your issue tracking system. After refining the issue breakdown through user interaction, the Skill publishes the independently grabbable issues to the tracker with proper triage labels and dependencies.

Do I need to manually review the issues generated from my PRD?

Yes, you need to manually review the issues generated from your PRD. The Skill requires user interaction to iterate on the issue breakdown, ensuring you provide refinement and final approval before any issues are published to the tracker.

What is the best way to convert a specification into actionable issue tickets?

The best way to convert a specification into actionable issue tickets is using vertical slicing to ensure comprehensive coverage. This approach creates independently grabbable issues and applies proper triage labels and dependencies during issue creation.

Why use vertical slicing instead of horizontal layers for plan breakdown?

Vertical slicing is used for plan breakdown instead of horizontal layers to ensure each issue is independently grabbable and covers end-to-end functionality. This method streamlines issue creation by maintaining comprehensive coverage across the entire project management workflow.