to-issues

Break plans, specs, and PRDs into dependency-ordered project issues.

Updated May 28, 2026

Search Tags:#planning #issue tracker #issues #prd #vertical slices #tracer bullet

Ready to run

npx skills add https://github.com/haryelramalho/skills --skill to-issues-haryelramalho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/to-issues
Command: npx skills add https://github.com/haryelramalho/skills --skill to-issues-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a plan, spec, or PRD into independently actionable issues for the project tracker, so teams can move from broad ideas to thin, demoable slices quickly.

Core Features & Use Cases

Breaks work into tracer-bullet vertical slices that cut through schema, API, UI, and tests end to end.
Organizes issues with blockers and dependency order so the work can be published in a sensible sequence.
Ideal for translating a roadmap, feature spec, or parent issue into AFK-ready tickets with clear acceptance criteria.

Quick Start

Ask to break the provided plan into tracker-ready vertical-slice issues and include titles, blockers, and acceptance criteria.

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 vertical slices for an issue tracker?▼

To break a PRD into vertical slices, decompose the plan into tracer-bullet issues that cut through schema, API, UI, and tests end to end. This ensures each slice is thin, demoable, and independently actionable for the tracker.

What are tracer-bullet vertical slices in project planning?▼

Tracer-bullet vertical slices are thin, end-to-end segments of work that cut through all layers of a system, from schema to UI and tests. They ensure each tracker issue is independently grabbable, demoable, and ready for AFK agents.

How do I organize issue dependencies when publishing a parent issue decomposition?▼

You organize issue dependencies by identifying blockers and mapping the dependency order during parent issue decomposition. This allows you to publish tracker-ready issues in a sensible sequence that respects execution constraints.

Do I need to provide acceptance criteria to generate tracker-ready issues?▼

Yes, you need to provide acceptance criteria to generate tracker-ready issues. The criteria ensure each vertical slice remains demoable and ready for AFK agents, while you must also supply your specific tracker vocabulary.

Can I use a feature spec to create AFK-ready tickets with clear blockers?▼

Yes, you can translate a feature spec or roadmap into AFK-ready tickets. The process breaks specs into vertical-slice issues with titles, defined blockers, dependency order, and acceptance criteria for each demoable slice.

What is the best way to prepare a roadmap for parent issue decomposition?▼

The best way to prepare a roadmap for parent issue decomposition is to provide contextual codebase or issue references alongside your tracker vocabulary. This allows the breakdown to generate dependency-aware, demoable vertical slices.