to-issues

Break plans, specs, or PRDs into dependency-ordered vertical-slice issues.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill to-issues-mattbutlerengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/mattbutlerengineering/mattbutlerengineering/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill to-issues-mattbutlerengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert a plan, spec, or PRD into independently-grabbable issues, so work can be tracked, delegated, and triaged efficiently without losing the end-to-end intent.

Core Features & Use Cases

  • Vertical-slice issue breakdown: Breaks work into tracer-bullet slices that cut through schema, API, UI, and tests end-to-end rather than reorganizing tasks by layer.
  • Dependency-aware structuring: Identifies blockers and establishes an execution order so new issues can reference real prerequisites.
  • HITL vs AFK selection: Marks slices as HITL when human decisions are required (e.g., architectural or design reviews) and prefers AFK when implementation and merge can proceed without human gating.

Quick Start

Use the to-issues skill to ask an AI to break your PRD or plan into HITL/AFK vertical-slice issues and publish them to your project 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 convert a PRD into GitHub issues for project planning?

To convert a PRD into GitHub issues, break the spec into independently-grabbable vertical-slice tickets that cut through schema, API, UI, and tests end-to-end for efficient tracking and delegation.

What is a vertical slice issue decomposition for engineering roadmaps?

Vertical slice issue decomposition breaks work into tracer-bullet slices that cut through schema, API, UI, and tests end-to-end, rather than reorganizing tasks by layer, preserving the end-to-end execution intent.

How do I map dependencies when breaking down a spec into implementation tickets?

Mapping dependencies during issue breakdown involves identifying blockers and establishing an execution order so newly published implementation tickets can reference real prerequisites in dependency order.

What is the difference between HITL and AFK slices in issue tracking?

HITL slices require human decisions for architectural or design reviews, while AFK slices allow implementation and merge to proceed without human gating, optimizing the issue tracker workflow.

Can I use this approach to create a tracer-bullet decomposition for end-to-end execution?

Yes, tracer-bullet decomposition is supported by drafting dependency-respecting vertical slices that cut end-to-end through the stack, getting user approval, and publishing issues using a required template.

Does issue decomposition work for tracking product and engineering work definitions?

Yes, issue decomposition applies to converting product and engineering work definitions into implementation tickets and roadmaps, enabling work to be tracked, delegated, and triaged efficiently.