to-issues

Convert plans, specs, or PRDs into tracer-bullet vertical slice issues.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --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/tree/main/skills/engineering/to-issues
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill to-issues-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down high-level plans, specifications, or PRDs into a set of independently-grabbable issues that can be tracked and completed end-to-end.

Core Features & Use Cases

  • Create tracer-bullet vertical slices that ensure coverage across all integration layers.
  • Produce concrete issues with clear scope, acceptance criteria, and dependencies.
  • Use for planning, triage, and handoffs between product, design, and development teams.

Quick Start

Provide a project plan reference and generate a prioritized list of end-to-end issues.

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 project plan into actionable issues?

To break a project plan into actionable issues, provide the plan or PRD reference to generate a prioritized list of end-to-end issues using tracer-bullet vertical slices. Each issue is independently grabbable with clear scope, acceptance criteria, and dependencies for ordered execution.

What is the best way to triage a PRD into trackable work items?

The best way to triage a PRD into trackable work items is converting high-level specifications into concrete issues with clear acceptance criteria and dependencies. This enables effective handoffs between product, design, and development teams by making scope explicit.

Can I use this for planning and triage workflows across product and development teams?

Yes, you can use this for planning and triage workflows across product and development teams. It converts high-level plans into concrete, trackable work items, enabling seamless handoffs and ensuring all integration layers are covered with explicit HITL or AFK status.

Do I need to define acceptance criteria before generating issues from a spec?

No, you do not need to define acceptance criteria before generating issues from a spec. The process produces concrete issues that automatically include clear scope, acceptance criteria, and dependencies to order work, explicitly marking HITL or AFK status when appropriate.

Why use tracer-bullet vertical slices instead of horizontal layers for project tracking?

Tracer-bullet vertical slices are used instead of horizontal layers for project tracking because they ensure end-to-end coverage across all integration layers. This creates independently grabbable issues that deliver trackable value through the full stack, rather than incomplete horizontal components.