skills.rest
paialex
paialexCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans, specs, or PRDs into GitHub issues with vertical slices.

1|Updated Feb 13, 2026
Search Tags:#workflow#github#issues#sprint-planning#tracer-bullet#plan-breakdown
One-click install
npx skills add https://github.com/paialex/ai-skills-bank --skill to-issues-paialex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/paialex/ai-skills-bank/tree/main/mattpocock_skills/engineering/to-issues
Command: npx skills add https://github.com/paialex/ai-skills-bank --skill to-issues-paialex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break plans, specs, or PRDs into independently-grabbable GitHub issues using tracer-bullet vertical slices.

Core Features & Use Cases

  • End-to-end slicemaking: decompose high-level plans into small, trackable issues that slice across API, UI, and tests.
  • Context-driven drafting: leverage existing conversation context and optional codebase exploration to inform slice creation.
  • GitHub-issue templating: generate standardized issue bodies with a parent, acceptance criteria, and blocker references.

Quick Start

Provide your plan or PRD and I will convert it into a set of tracer-bullet GitHub 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 down a PRD into GitHub issues for sprint planning?▼

To break down a PRD into GitHub issues, you provide the high-level documentation and the plan is decomposed into small, trackable issues using tracer-bullet vertical slices that span across API, UI, and tests for sprint planning.

What is a tracer-bullet vertical slice in issue creation?▼

A tracer-bullet vertical slice is an issue decomposition strategy that drafts end-to-end tasks cutting across API, UI, and tests, ensuring each generated issue is independently grabbable by engineers during sprint execution.

Can I use existing codebase context to generate GitHub issues from a spec?▼

Yes, you can use existing codebase context to generate GitHub issues. The process optionally explores the codebase alongside conversation context to inform the creation of standardized issue bodies with acceptance criteria.

What is the best way to structure GitHub issues for independent task grabbability?▼

The best way to structure GitHub issues for independent grabbability is generating them from a standardized template that includes parent references, acceptance criteria, and blocker references using deterministic end-to-end slices.

Does generating issues from a plan require manual validation of the breakdown?▼

Generating issues from a plan includes a validation step where the system quizzes the user on the drafted end-to-end slices before finalizing the GitHub issues, ensuring the plan breakdown accurately reflects intent.

Related Skills

Explore More Software Engineering Skills→
cloudofgeorgecloudofgeorge

to-issues

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

Community
Advanced
officechbusinessservices-creatorofficechbusinessservices-creator

prd-to-issues

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

Community
Advanced
TasupTasup
2

update-parent-issue-status

Update parent GitHub Issues based on child issue status changes.

Official
Advanced
dgowriedgowrie

prd-to-issues

Convert a PRD into dependency-ordered GitHub issues with vertical slices.

Community
Intermediate