to-issues

Convert project plans into GitHub issues using vertical slicing.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Varadraj13/zone-of-classification --skill to-issues-varadraj13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Varadraj13/zone-of-classification/tree/main/Core_skills/to-issues
Command: npx skills add https://github.com/Varadraj13/zone-of-classification --skill to-issues-varadraj13

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill aids in transforming plans, specifications, or PRDs into manageable GitHub issues through the use of vertical slices, streamlining the process of creating and organizing tasks.

Core Features & Use Cases

  • Plan Decomposition: Breaks down complex plans into smaller, actionable GitHub issues.
  • Vertical Slicing: Implements a method where issues are created as end-to-end slices that span all layers of the system.
  • User Interaction: Allows the user to review and refine the issue breakdown before finalizing it.
  • Use Case: Ideal for teams that need to convert a project plan into a series of implementable GitHub issues, ensuring that each issue is clear, independent, and testable.

Quick Start

Run the to-issues skill with your plan document as input to generate a structured set of GitHub issues.

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 project plan into GitHub issues using vertical slicing?

To break down a project plan into GitHub issues using vertical slicing, input your plan document to generate structured, end-to-end actionable tasks spanning all system layers. You can review and refine these issues before finalizing them.

What is vertical slicing in software development project management?

Vertical slicing in software development is a plan decomposition method where issues are created as end-to-end slices spanning all layers of the system. This technique ensures each issue is clear, independent, and testable.

Do I need the GitHub API and gh installed to convert plans into issues?

Yes, you need the GitHub API for issue creation and the gh dependency installed. You also need access to the project's repository to successfully create and organize the tasks.

Can I review and refine GitHub issues before they are finalized?

Yes, you can review and refine the issue breakdown before finalizing it. The skill allows user interaction to ensure the vertical slices are clear, independent, and testable before committing them to your repository.

What's the best way to transform a PRD into implementable GitHub issues?

The best way to transform a PRD into implementable GitHub issues is using vertical slicing techniques. This ensures each issue spans all system layers end-to-end, making them clear, independent, and testable for development teams.