skills.rest
shushuzn
shushuznCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans, specs, or PRDs into dependency-ordered vertical slice issues.

4|Updated Mar 2, 2026
Search Tags:#github issues#delivery planning#vertical slicing#product spec#dependency ordering#triage labels#issue breakdown
One-click install
npx skills add https://github.com/shushuzn/Rairos --skill to-issues-shushuzn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/shushuzn/Rairos/tree/main/skills/to-issues
Command: npx skills add https://github.com/shushuzn/Rairos --skill to-issues-shushuzn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert a plan, spec, or PRD into a set of implementation-ready issues that can be tackled independently, reducing ambiguity and speeding up execution.

Core Features & Use Cases

  • Tracer-bullet vertical slicing: Breaks work into thin, end-to-end slices that cut through all relevant integration layers.
  • HITL vs AFK labeling: Marks slices that need human decisions versus those that can be implemented and merged directly.
  • Dependency-aware publishing: Orders issue creation by blockers so teams can start in the correct sequence.
  • Issue content that aligns with project vocabulary: Encourages domain glossary consistency and ADR-respecting wording.

Quick Start

Ask to-issues to break the provided plan into tracer-bullet issues and publish them to the project issue tracker using the existing triage label vocabulary.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I convert a PRD into GitHub issues that developers can work on independently?▼

Tracer-bullet vertical slicing is a technique that breaks a product spec into thin, end-to-end issues cutting through all integration layers, ensuring each slice is independently grabbable and verifiable before moving to the next dependency.

How do I order GitHub issues by dependencies so my team starts in the correct sequence?▼

Dependency-aware publishing orders issue creation by blockers, allowing teams to start in the correct sequence. The system drafts thin tracer-bullet slices and quizzing you for dependency correctness before publishing approved issues.

What's the best way to break down a product spec into implementation tickets?▼

The best way to break down a product spec into implementation tickets requires drafting thin tracer-bullet vertical slices, applying HITL versus AFK triage labels, and aligning issue content with the project's domain glossary and ADR wording.

Can I use existing triage labels when publishing issues from a plan?▼

Yes, you can publish issues to the project issue tracker using the existing triage label vocabulary. The process encourages domain glossary consistency and ADR-respecting wording to align with your project's established conventions.

Does converting a plan to issues require reviewing the codebase first?▼

Reviewing the codebase is optional when converting a plan to issues. The process requires fetching referenced issues when given, optionally reviewing the codebase, and then drafting thin tracer-bullet slices before quizzing you for granularity.

Related Skills

Explore More Product & Management Skills→
ThorStarlordThorStarlord
1

to-issues

Break plans into dependency-ordered issue tracker tickets with triage labels.

Community
Advanced
IsKenKenYaIsKenKenYa

to-issues

Break plans, specs, or PRDs into vertical-slice issues with dependency order.

Community
Intermediate
darkmatterdarkmatter
1

improve-codebase-architecture

Detect shallow modules and propose deepening refactors using project glossary and ADRs.

Official
Advanced
MichaelSolatiMichaelSolati

to-issues

Break down project plans, specs, and PRDs into structured vertical-slice issues.

Community
Intermediate