to-issues

Decompose plans or PRDs into vertical-slice issues as Markdown or GitHub issues.

5|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill to-issues-outlinedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/to-issues
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill to-issues-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose plans, PRDs, or specs into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.

Core Features & Use Cases

  • Break plans into tracer-bullet vertical slices that cross schema, API, UI, and tests and are independently demoable.
  • Emit slices to a Markdown file by default or create GitHub issues via a flag, in dependency order to resolve blockers.

Quick Start

Provide a plan file path and request emission of vertical slices as 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 a PRD into trackable implementation issues?

To break a PRD into trackable implementation issues, this Skill decomposes product specifications into independently-grabbable vertical-slice tickets. It emits a markdown file of slices by default, or creates GitHub issues directly when triggered with a flag.

What are vertical-slice issues in project planning?

Vertical-slice issues are work items that cross schema, API, UI, and tests end-to-end. This approach ensures each slice is independently demoable and parallelizable, resolving dependencies and blockers through ordered task creation.

Can I create GitHub issues automatically from a plan file?

Yes, you can create GitHub issues automatically from a plan file by using a specific flag. The Skill parses the implementation plan and generates issues in dependency order, ensuring idempotent updates and blocker references.

Does issue tracking work with markdown files instead of GitHub?

Yes, issue tracking works with markdown files by default. The Skill outputs decomposed vertical slices into a markdown file, allowing teams to review work breakdown locally before optionally exporting to GitHub issues.

What is the best way to parallelize work from a product specification?

The best way to parallelize work from a product specification is decomposing it into tracer-bullet vertical slices. This method creates independently grabbable issues across schema, API, UI, and tests, ordered by dependencies to clear blockers.