to-issues

Split project documentation into traceable issues for issue trackers.

Updated Mar 12, 2026

Search Tags:#project management #issue tracking #issue creation #vertical slicing #tracer bullet

Ready to run

npx skills add https://github.com/GuitarAlchemist/ix --skill to-issues-guitaralchemist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/GuitarAlchemist/ix/tree/main/.claude/skills/to-issues
Command: npx skills add https://github.com/GuitarAlchemist/ix --skill to-issues-guitaralchemist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in breaking down project plans, specifications, or PRDs into smaller, independently trackable issues in a project's issue tracker.

Core Features & Use Cases

Vertical Slice Issues: Splits the project into complete end-to-end slices, reducing dependencies and improving traceability.
User Story Mapping: Generates issues based on user stories to align work with project requirements.
Issue Tracker Integration: Publishes the generated issues directly into the issue tracker for streamlined workflow.

Quick Start

Create a new issue by running the skill with the /to-issues command, specifying your project's plan, spec, or PRD.

Frequently Asked Questions about to-issues

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

FAQPage Schema

How do I split high-level project documentation into trackable issues?▼

To split project documentation into trackable issues, this skill breaks down project plans, specs, or PRDs into smaller, independently traceable items for issue trackers. It transforms high-level documentation into discrete development tasks.

What is vertical slicing in issue creation and how does it reduce dependencies?▼

Vertical slicing in issue creation splits a project into complete end-to-end slices, reducing dependencies and improving traceability. This approach generates issues that represent independently deliverable units of work across the project stack.

How do I generate issues from user stories to align work with project requirements?▼

You generate issues from user stories to align work with project requirements through user story mapping. This process translates mapped user journeys into discrete, actionable issues that directly reflect the original project requirements.

Can I publish generated issues directly into my project's issue tracker?▼

Yes, you can publish generated issues directly into your project's issue tracker. This skill integrates with issue tracking systems to facilitate streamlined planning, review, and execution workflows without manual data entry.

How do I create issues from a PRD for software development task tracking?▼

To create issues from a PRD for software development task tracking, run the skill with your project's plan, specification, or PRD. It automatically splits the documentation into a series of traceable issues for managing development tasks.

When should I use vertical slice issues instead of horizontal layer issues?▼

Use vertical slice issues when you need to reduce dependencies and improve traceability across complete end-to-end project slices. Horizontal layer issues create cross-dependencies between teams, making independent delivery and progress tracking more difficult.