pac-to-issues

Break down plans or PRDs into dependency-ordered GitHub issues.

2|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/ladislas/mypac --skill pac-to-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pac-to-issues
Source: https://github.com/ladislas/mypac/tree/main/skills/pac-to-issues
Command: npx skills add https://github.com/ladislas/mypac --skill pac-to-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a plan, PRD, or discussion into independently-grabbable GitHub issues using tracer bullets.

Core Features & Use Cases

  • Break plans into tracer-bullet vertical slices; each slice is a complete path that can be implemented end-to-end.
  • Classify slices as HITL or AFK; define dependencies and blockers; promote many thin slices over few thick ones.
  • Provide a guided workflow for user questions, then create and wire issues in the repository in dependency order, linking parent and sub-issues and updating task-tracking sections.

Quick Start

Convert a product plan or PRD into a linked set of GitHub issues using tracer bullets.

Frequently Asked Questions about pac-to-issues

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

FAQPage Schema
How do I convert a PRD into linked GitHub issues?

To convert a PRD into linked GitHub issues, this Skill breaks down the plan into tracer-bullet vertical slices. It then creates and wires these issues in dependency order, linking parent and sub-issues directly within your repository.

What are tracer bullets in feature development planning?

Tracer bullets in feature development planning are thin, complete vertical slices that can be implemented end-to-end. This approach promotes many thin slices over thick ones to decompose plans into independently actionable development tasks.

Do I need gh CLI access to create GitHub issues from a plan?

Yes, you need gh CLI access to create GitHub issues from a plan. The Skill requires this environment setup to execute a guardrail-driven workflow and automatically wire dependencies, blockers, and parent relationships.

How are development tasks classified when decomposing a plan?

When decomposing a plan, development tasks are classified as HITL (human-in-the-loop) or AFK (away-from-keyboard). This classification helps define dependencies and blockers for each vertical slice during issue creation.

What is the best way to break down a product plan into vertical slices?

The best way to break down a product plan into vertical slices is applying a guided workflow with guardrail rules. This method ensures each slice is independently grabbable and generates a dependency-ordered set of interlinked issues.