to-issues

Break down text-based plans into actionable issues for issue trackers.

1|1|Updated Feb 4, 2026

Search Tags:#project management #issue tracker #issue creation #vertical slicing #plan breakdown

Ready to run

npx skills add https://github.com/arxxyr/dotfiles --skill to-issues-arxxyr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/arxxyr/dotfiles/tree/main/dot_agents/skills/to-issues
Command: npx skills add https://github.com/arxxyr/dotfiles --skill to-issues-arxxyr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill breaks down complex plans, specifications, or PRDs into manageable issues, making it easier to create implementation tickets and organize work effectively.

Core Features & Use Cases

Plan Breakdown: Converts a high-level plan into a list of independent issues.
Issue Creation: Generates issues in a project issue tracker based on the plan's vertical slices.
Use Case: When you have a detailed project plan and need to translate it into actionable items for your team.

Quick Start

Run the command '/to-issues my-plan.md' to convert your plan document into issues.

Frequently Asked Questions about to-issues

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

FAQPage Schema

How do I convert a PRD into actionable issues for an issue tracker?▼

To convert a PRD into actionable issues, you need a plan breakdown tool that parses text-based specifications and outputs independent issues structured by vertical slices for direct integration into your issue tracker.

What is vertical slicing in plan breakdown and when do I need it?▼

Vertical slicing in plan breakdown splits specifications into independent, end-to-end issues. You need it when translating high-level plans into actionable items to ensure each issue delivers standalone functional value.

How do I break down a markdown plan into issues step by step?▼

To break down a markdown plan into issues, point a plan breakdown utility at your text file. It parses the document, applies vertical slicing, and generates a structured list of actionable tickets for your project.

Do I need a configured issue tracker and label vocabulary before generating issues?▼

Yes, you need a configured issue tracker and a predefined label vocabulary. These prerequisites ensure the generated issues match your project's tracking environment and categorization standards.

Can I refine issue granularity after the initial plan breakdown?▼

Yes, you can refine issue granularity after the initial plan breakdown. The process handles user feedback to adjust the size and scope of the generated vertical slices within your actionable issues.