to-issues

Converts plans and PRDs into vertical-slice issues on a project issue tracker.

Updated May 18, 2024
One-click install
npx skills add https://github.com/joshhornby/dotfiles --skill to-issues-joshhornby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/to-issues
Command: npx skills add https://github.com/joshhornby/dotfiles --skill to-issues-joshhornby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable tickets is slow and often produces horizontal, layer-by-layer tasks that cannot be shipped independently. This Skill breaks work into thin vertical slices and publishes them as ready-to-grab issues on your issue tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Splits a plan into end-to-end vertical slices that cut through schema, API, UI, and tests, so each issue is independently demoable. - HITL vs AFK classification: Marks each slice as requiring human interaction (HITL) or fully autonomous (AFK), preferring AFK where possible. - Interactive review loop: Presents the proposed breakdown with titles, types, dependencies, and covered user stories, then iterates with the user until approved. - Tracker publishing: Creates issues in dependency order using a structured template with acceptance criteria and blocker references, applying the correct triage label. - Use Case: After drafting a PRD for a new feature, run this Skill to produce a set of dependency-ordered issues that AFK agents can pick up immediately. ## Quick Start Ask the assistant to break the current plan or PRD into independently-grabbable issues and publish them to the issue tracker.

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 implementation issues?

Provide the plan, spec, or PRD in the conversation and the Skill drafts tracer-bullet vertical slices, each cutting through all layers end-to-end. You review the proposed titles, dependencies, and user story coverage, then approve before issues are published to the tracker.

What is a vertical slice or tracer-bullet issue?

A vertical slice is a thin but complete path through every integration layer, such as schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own.

What is the difference between HITL and AFK slices?

HITL slices require human interaction, such as an architectural decision or design review, while AFK slices can be implemented and merged without human involvement. The Skill prefers AFK slices wherever possible.

Does this Skill modify or close the parent issue?

No. The Skill only references the parent issue in the new issue bodies and explicitly does not close or modify it. It publishes new child issues in dependency order with blocker references.

What issue tracker setup is required before using this Skill?

The issue tracker and triage label vocabulary must already be provided to the assistant, for example by running the referenced setup command. Published issues receive the correct triage label so AFK agents can pick them up.