to-issues

Breaks plans and PRDs into vertical-slice issues on the project issue tracker.

2|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Nzettodess/Awesome-Agent-Skills --skill to-issues-nzettodess
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Nzettodess/Awesome-Agent-Skills/tree/main/Skills/Engineering%20Skills/skills/engineering/to-issues
Command: npx skills add https://github.com/Nzettodess/Awesome-Agent-Skills --skill to-issues-nzettodess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable work items is slow and error-prone, and horizontal task breakdowns often produce issues that cannot be shipped or verified independently. This Skill converts planning material into thin, end-to-end vertical slices published directly to the issue tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Splits a plan into thin vertical slices that cut through all layers (schema, API, UI, tests) so each issue is independently demoable. - HITL vs AFK classification: Marks each slice as requiring human interaction or safe for autonomous implementation, with dependency ordering between slices. - Interactive review loop: Presents the proposed breakdown for user approval on granularity, dependencies, and slice merging before publishing. - Structured issue publishing: Creates issues in dependency order using a template with parent reference, description, acceptance criteria, and blockers, plus the correct triage label. - Use Case: After finalizing a PRD for a new feature, run this Skill to produce a set of ready-to-grab tracker issues that AFK agents can implement in parallel. ## Quick Start Ask the agent to break the current plan or PRD into 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 conversation and the Skill drafts tracer-bullet vertical slices, each cutting through all layers end-to-end. You review the breakdown for granularity and dependencies, then it publishes the approved issues to the tracker.

What is a vertical slice issue breakdown?▼

A vertical slice is a thin issue that delivers a complete path through every layer, such as schema, API, UI, and tests, rather than one horizontal 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. AFK slices can be implemented and merged without human involvement, and the Skill prefers AFK wherever possible.

Does this Skill modify or close the parent issue?▼

No. It references the parent issue in each new issue body but explicitly does not close or modify it. New issues are published in dependency order with the correct triage label.

When should I not use vertical slice decomposition?▼

Avoid it when work cannot be demoed end-to-end, such as pure refactors or infrastructure changes with no user-visible path. In those cases a conventional task breakdown may fit better.