to-issues

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

Updated May 12, 2026
One-click install
npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill to-issues-eduardtomasek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/eduardtomasek/codex-dev-stack/tree/main/skills/.agents/to-issues
Command: npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill to-issues-eduardtomasek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable tracker tickets is slow and often produces horizontal, layer-by-layer tasks that cannot be shipped independently. This Skill breaks work into thin vertical slices that are each demoable and ready for autonomous agents to pick up. ## Core Features & Use Cases - Tracer-bullet slicing: Splits a plan into end-to-end vertical slices that cut through schema, API, UI, and tests rather than single layers. - HITL vs AFK classification: Marks each slice as requiring human interaction or safe for autonomous implementation, preferring AFK where possible. - Interactive refinement: Presents the proposed breakdown with dependencies and 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. - Use Case: After drafting a feature PRD, ask the agent to convert it into issues; it proposes slices, confirms granularity with you, then publishes labeled, dependency-linked tickets to your issue tracker. ## Quick Start Ask the agent 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 conversation and the Skill drafts tracer-bullet vertical slices, each cutting through all layers end-to-end. You review the breakdown, adjust granularity and dependencies, then it publishes the issues to your tracker.

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

A vertical slice is a thin but complete path through every layer of the system, 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 the Skill publish issues automatically without review?▼

No. It presents the proposed breakdown as a numbered list with titles, types, blockers, and user stories, then quizzes you on granularity and dependencies. Issues are only published after you approve the breakdown.

What setup is required before creating issues from a plan?▼

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 it cannot publish labeled issues.