to-issues

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill to-issues-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/to-issues
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill to-issues-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable work items often produces horizontal, layer-by-layer tasks that cannot be demoed or picked up independently. This Skill decomposes plans into tracer-bullet vertical slices and publishes them as ready-to-grab issues on the project issue tracker. ## Core Features & Use Cases - Vertical Slice Breakdown: Splits a plan into thin end-to-end slices that cut through all layers (schema, API, UI, tests) so each issue is independently demoable. - Interactive Refinement: Presents the proposed breakdown with titles, dependencies, and covered user stories, then iterates with the user until the granularity is approved. - Structured Issue Publishing: Publishes issues in dependency order using a consistent template with acceptance criteria and blocker references, applying the correct triage label for AFK agents. - Use Case: After drafting a feature PRD, invoke this Skill to convert it into a set of dependency-ordered tracker issues that teammates or autonomous agents can pick up immediately. ## 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 issues for my issue tracker?▼

Provide the plan, spec, or PRD in the conversation and invoke the Skill. It drafts tracer-bullet vertical slices, asks you to confirm granularity and dependencies, then publishes each approved slice as an issue with acceptance criteria and blocker references.

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 demoable or verifiable on its own.

Can I use this with an existing issue instead of a plan?▼

Yes. Pass an issue number, URL, or path as an argument and the Skill fetches the full body and comments from the issue tracker, then uses that as the source material for the breakdown.

Does the breakdown respect existing architecture decisions?▼

Yes. The Skill optionally explores the codebase first so issue titles and descriptions use the project's domain glossary vocabulary and respect ADRs in the affected area. It also looks for prefactoring opportunities before slicing.

When should I not split work into vertical slices?▼

Avoid vertical slicing when the work is a single-layer change with no cross-cutting behavior, such as a pure copy edit or config tweak. The approach is designed for features spanning multiple integration layers.