skills.rest
truongnat
truongnatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-issues-pro

Decompose PRDs into GitHub issues with vertical slices and HITL or AFK classification.

Updated Jun 27, 2026
Search Tags:#software development#GitHub issues#vertical slices#issue decomposition#PRD analysis
One-click install
npx skills add https://github.com/truongnat/aix --skill to-issues-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues-pro
Source: https://github.com/truongnat/aix/tree/main/content/skills/to-issues-pro
Command: npx skills add https://github.com/truongnat/aix --skill to-issues-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users break down complex plans and PRDs into manageable, independently-implementable GitHub issues, streamlining the development process.

Core Features & Use Cases

  • Issue Decomposition: Converts high-level plans and PRDs into detailed GitHub issues.
  • Vertical Tracer-Bullet Slices: Ensures each issue is a complete path through all layers (UI → API → DB).
  • Classification: Tags issues as HITL (requires human review) or AFK (can be implemented autonomously).
  • Use Case: Ideal for users with a spec or PRD who need to create a structured issue backlog.

Quick Start

Use the to-issues-pro skill to break down the 'checkout PRD' into GitHub issues.

Frequently Asked Questions about to-issues-pro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a PRD into GitHub issues?▼

To break down a PRD into GitHub issues, you can use issue decomposition to transform high-level plans into detailed, actionable items. This process streamlines development by converting complex specs into manageable tasks.

What are vertical slices in issue decomposition?▼

Vertical slices in issue decomposition are complete paths through all project layers, such as UI to API to DB. They ensure each GitHub issue forms a vertical tracer-bullet slice for independent implementation.

How do I classify GitHub issues for autonomous implementation?▼

You classify GitHub issues for autonomous implementation by tagging them as AFK, meaning they can be implemented without human oversight. Issues requiring manual review are tagged as HITL.

Can I use a spec to create a structured GitHub issue backlog?▼

Yes, you can use a spec or PRD to create a structured GitHub issue backlog. Issue decomposition transforms these high-level plans into independently-implementable items, streamlining the development process.

Do I need GitHub access to decompose plans into vertical slices?▼

Yes, you need GitHub access to decompose plans into vertical slices. Additionally, understanding the project's layers is required to ensure each issue forms a complete path through the architecture.

Related Skills

Explore More Software Engineering Skills→
softmgsoftmg

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning via CLI.

Official
Advanced
fray-cloudfray-cloud

prd-to-issues

Break a PRD into dependency-ordered GitHub issues using tracer-bullet vertical slices.

Community
Intermediate
MaggieAppletonMaggieAppleton
160

prd-to-issues

Convert PRDs into GitHub issues with tracer-bullet vertical slices.

Community
Advanced
assofohdzassofohdz
25

to-issues

Convert unstructured project plans into ordered issue tracker tickets with dependencies.

Community
Intermediate