to-issues

Breaks down plans, specs, or PRDs into tracer-bullet vertical slices with schema, API, UI, and tests.

Updated Nov 16, 2022
One-click install
npx skills add https://github.com/kos3nz/dotfiles --skill to-issues-kos3nz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/kos3nz/dotfiles/tree/main/.config/agents/skills/to-issues
Command: npx skills add https://github.com/kos3nz/dotfiles --skill to-issues-kos3nz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting a plan, spec, or PRD into a structured, slicable set of issues that can be tackled independently on the project's issue tracker.

Core Features & Use Cases

  • Break down a plan into small, end-to-end vertical slices that span all layers (API, UI, tests, and data).
  • Generate implementation tickets with clear scope, acceptance criteria, and user stories aligned to project terminology.
  • Use tracer bullets to ensure each slice delivers a complete path through the system and can be validated in isolation.

Quick Start

Provide your plan, PRD, or spec text, and I will break it into tracer-bullet vertical-slice 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 PRD into vertical slice issues for an issue tracker?

To break down a PRD into vertical slice issues, the Skill parses your plan text and divides it into end-to-end tracer-bullet slices. Each generated issue spans all layers, including schema, API, UI, and tests, ready for publication.

What is a tracer bullet issue in software project planning?

A tracer bullet issue is an end-to-end vertical slice that delivers a complete path through the system. It spans API, UI, tests, and data layers, allowing each slice to be validated in isolation and grabbed independently by developers.

How do I generate issue tickets with acceptance criteria from a project spec?

You can generate issue tickets with acceptance criteria by providing your project spec to the Skill. It produces a structured proposal for each slice, including titles, user stories, acceptance criteria, and known blockers, aligned to project terminology.

Can I use project glossaries and ADRs when creating actionable issue slices?

Yes, you can use project glossaries and ADRs when creating actionable issue slices. The Skill applies available project glossary vocabulary and architecture decision records to ensure generated tickets match your established terminology and constraints.

Does this issue breakdown method work for large specs with many dependencies?

The issue breakdown method works for large specs by generating slices designed to be tackled independently. It identifies blockers for each slice, ensuring dependencies are surfaced so teams can validate end-to-end functionality without hidden conflicts.

Why convert a plan into independently-grabbable tracer-bullet issues?

Converting a plan into independently-grabbable tracer-bullet issues ensures each slice delivers complete functionality across all layers. This allows parallel development, isolated validation, and clear scope tracking directly within your issue tracker.