to-issues

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

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill to-issues-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/core/dependencies/github/to-issues
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill to-issues-dagimalemayehuu

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 block each other and cannot be demoed independently. This Skill breaks a plan into thin vertical slices and publishes them as ready-to-grab issues on the project issue tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Splits work into thin 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 approval loop: Presents the proposed breakdown with titles, types, dependencies, and covered user stories, then iterates with the user until approved. - Structured issue publishing: Publishes issues in dependency order using a template with parent reference, description, acceptance criteria, and blocked-by links, applying the correct triage label. - Use Case: After finalizing a feature PRD, ask the agent to break it into issues; it proposes five vertical slices, you adjust the granularity, and it publishes labeled, dependency-linked issues ready for AFK agents to implement. ## Quick Start Use the to-issues skill to break this approved plan into vertical-slice 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 plan or PRD into GitHub issues?▼

Provide the plan, spec, or PRD in the conversation and invoke the skill. It drafts tracer-bullet vertical slices, asks you to approve the granularity and dependencies, then publishes each approved slice as an issue with acceptance criteria and blocked-by links.

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

A vertical slice is a thin piece of work 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 where possible and asks you to confirm the classification.

Does the skill modify or close the parent issue?▼

No. The skill only references the parent issue in each new issue's body and explicitly does not close or modify it. New issues are published in dependency order so blockers can be linked by real identifiers.

What setup is required before creating issues with this skill?▼

The issue tracker and triage label vocabulary must already be configured, which the skill notes is done by running the setup-matt-pocock-skills command. Without that context, the skill cannot publish issues with the correct triage labels.