to-issues

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

11|2|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/oskrgab/petrodb --skill to-issues-oskrgab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/oskrgab/petrodb/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/oskrgab/petrodb --skill to-issues-oskrgab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable work items is slow and often produces horizontal, layer-by-layer tickets that cannot be shipped independently. This Skill converts planning documents into thin, end-to-end vertical slices published directly to the issue tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Breaks work 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, preferring AFK where possible. - Interactive refinement: Presents the proposed breakdown with dependencies and user-story coverage, then iterates with the user before publishing. - Tracker publishing: Creates issues in dependency order with a structured template (What to build, Acceptance criteria, Blocked by) and applies the triage label. - Use Case: After drafting a PRD for a new feature, ask the assistant to break it into issues; it proposes 6 vertical slices, you adjust two, and it publishes them to the tracker with correct blocking relationships. ## Quick Start Break the attached feature spec 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 the conversation and ask for it to be broken into issues. The Skill drafts vertical slices, shows titles, types, dependencies, and user-story coverage, then publishes approved slices to the issue tracker.

What is a vertical slice or tracer-bullet issue?

A vertical slice is a thin piece of work that cuts through every layer of the system 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.

Can I adjust the issue breakdown before anything is published?

Yes. The Skill presents the proposed slices as a numbered list and asks about granularity, dependencies, and HITL/AFK classification. It only publishes to the tracker after you approve the breakdown.

Does it modify the parent issue when publishing slices?

No. The Skill references the parent issue in each new issue body but never closes or modifies it. New issues are published in dependency order with the needs-triage label applied.