to-issues

Convert project plans, specifications, or PRDs into independently demoable issues via vertical slicing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts complex plans, specifications, or PRDs into manageable issues suitable for project issue tracking, streamlining the process of breaking down work into actionable tasks.

Core Features & Use Cases

  • Vertical Slicing: Breaks down plans into end-to-end, independently demoable slices.
  • Issue Tracker Integration: Automatically creates issues in your project's issue tracker.
  • User Interaction: Provides a guided process for user input and review, ensuring the breakdown aligns with project needs.
  • Use Case: When you have a large project plan and need to create detailed issues for your development team.

Quick Start

Run the 'to-issues' skill with the plan document as input.

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 issue tracking?

Vertical slicing is a project planning technique that breaks down plans into end-to-end, independently demoable slices. It transforms specifications into manageable issues, ensuring each task delivers functional value across the entire stack rather than isolating technical layers.

Can I use project plans to automatically create issues with vertical slicing?

To break down project specifications into actionable issues, provide the plan document as input. The guided process then interactively reviews the plan's context and structure, converting it into a series of end-to-end, demoable issues for your tracker.

Does issue creation with vertical slicing work without dependencies?

This vertical slicing approach differs from traditional task breakdown by creating independently demoable, end-to-end issues instead of isolated technical tasks. It ensures each generated issue delivers functional value, facilitating better issue tracking and structured project management.

What are the limitations of vertical slicing for task breakdown?

A limitation of vertical slicing for task breakdown is its dependency on user input. It requires you to provide the plan's context and structure interactively, meaning it cannot autonomously generate actionable issues without guided human review and specification.