to-issues

Breaks a plan, spec, or PRD into dependency-ordered GitHub issues with HITL/AFK classification.

Updated May 25, 2026
One-click install
npx skills add https://github.com/AcendWay/ai-skills-library --skill to-issues-acendway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/AcendWay/ai-skills-library/tree/main/skill-folders/to-issues
Command: npx skills add https://github.com/AcendWay/ai-skills-library --skill to-issues-acendway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert a plan, spec, or PRD into actionable GitHub issues so work can start faster and implementation stays well-scoped end-to-end.

Core Features & Use Cases

  • Vertical-slice issue breakdown: Produces thin, independently-grabbable issues that cut through all integration layers (schema, API, UI, tests) to avoid partial or hard-to-verify tickets.
  • HITL vs AFK classification: Marks slices that require human interaction (e.g., architectural decisions/design review) versus slices that can be implemented and merged without it.
  • Dependency-aware creation: Creates issues in dependency order so “Blocked by” references real issue numbers and blockers are clear.
  • Use case: Break down a PRD for a new feature into multiple tracer-bullet issues that can be iterated, demoed, and verified independently (including which steps need review).

Quick Start

Ask it to break your plan or PRD into tracer-bullet GitHub issues, classify each slice as HITL or AFK, and then create the issues with correct dependency ordering.

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 GitHub issues?

To break a PRD into vertical slices, this Skill generates thin, independently-grabbable GitHub issues that cut through schema, API, UI, and test layers. It creates tracer-bullet slices so work stays well-scoped and individually verifiable.

What is the best way to automate GitHub issue creation with dependencies?

Automating GitHub issue creation with dependencies requires resolving issue numbers in order. This Skill creates GitHub issues via gh in dependency order, populating Blocked by relationships so blockers are clear and traceable.

How do I classify implementation tickets as HITL or AFK?

Classifying implementation tickets as HITL or AFK involves marking slices that require human interaction versus those that can merge without it. This Skill evaluates your PRD slices to separate architectural decisions from autonomous implementation work.

Can I use this to generate tracer-bullet issues from a spec document?

Yes, you can generate tracer-bullet issues from a spec document. This Skill translates engineering plans or specs into actionable work items, populating acceptance criteria and managing dependencies for each generated slice.

How to manage Blocked by relationships when creating multiple GitHub issues?

Managing Blocked by relationships requires creating GitHub issues in dependency order. This Skill generates an approval-checked breakdown first, then creates issues via gh, referencing real issue numbers to establish accurate Blocked by links.