to-issues

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

Updated Nov 23, 2024
One-click install
npx skills add https://github.com/tokisakiyuu/dotfiles --skill to-issues-tokisakiyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/tokisakiyuu/dotfiles/tree/main/home/dot_claude/skills/to-issues
Command: npx skills add https://github.com/tokisakiyuu/dotfiles --skill to-issues-tokisakiyuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable work items is slow and error-prone: teams often create horizontal, layer-by-layer tickets that cannot be demoed independently and create hidden dependencies. This Skill breaks a plan into thin, end-to-end vertical slices and publishes them as ready-to-grab issues on the project's issue tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Splits work into vertical slices that cut through all layers (schema, API, UI, tests) so each issue is independently demoable and verifiable. - 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, blockers, and covered user stories, then iterates with the user until approved. - Dependency-ordered publishing: Creates issues on the tracker in blocker-first order using a structured template with acceptance criteria and triage labels. - Use Case: After drafting a feature PRD, ask the agent to break it into issues; it proposes 6 vertical slices, you adjust granularity, and it publishes them to the tracker with correct blocking relationships. ## Quick Start Ask the agent to break the attached 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 or spec into implementation issues?▼

Provide the plan, spec, or PRD in the conversation and ask for it to be broken into issues. The Skill drafts vertical slices, quizzes you on granularity and dependencies, then publishes approved issues to your issue tracker in dependency order.

What is a vertical slice or tracer-bullet issue?▼

A vertical slice is a thin issue that cuts through all integration layers end-to-end, such as schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is independently demoable or verifiable.

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 work with any issue tracker?▼

The Skill expects an issue tracker and triage label vocabulary to already be configured in the environment, provided by the setup-matt-pocock-skills setup. It publishes issues with the correct triage label unless instructed otherwise.

Can I adjust the proposed issue breakdown before publishing?▼

Yes. The Skill presents the proposed slices as a numbered list with titles, types, blockers, and covered user stories, then asks about granularity, dependencies, and HITL/AFK classification. It iterates until you approve before publishing anything.