to-issues

Break product plans into dependency-aware issue tracker tasks with acceptance criteria.

Updated Jun 26, 2026

Search Tags:#project management #software development #issue tracker #prd #vertical slices #issue planning

Ready to run

npx skills add https://github.com/yash-garg/pi-config --skill to-issues-yash-garg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/yash-garg/pi-config/tree/main/skills/to-issues
Command: npx skills add https://github.com/yash-garg/pi-config --skill to-issues-yash-garg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps transform broad plans, specifications, or PRDs into clear, independently executable issues so teams can organize implementation work into complete deliverable slices.

Core Features & Use Cases

Vertical Slice Planning: Breaks initiatives into tracer-bullet issues that cover complete user-facing paths rather than isolated technical layers.
Issue Drafting Workflow: Creates structured issue proposals with titles, dependencies, user stories, descriptions, and acceptance criteria.
Use Case: A product team can provide a feature specification and use this Skill to produce a dependency-aware issue breakdown ready for review and publication in an issue tracker.

Quick Start

Ask the to-issues skill to break this product specification into independently grabbable implementation issues using vertical slices.

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 actionable engineering issues?▼

Vertical slice planning decomposes initiatives into tracer-bullet issues that cover complete user-facing paths, rather than isolated technical layers, ensuring each task delivers a complete slice of functionality.

Can I generate issue dependencies and acceptance criteria from a feature specification?▼

Yes, you can generate issue dependencies and acceptance criteria from a feature specification by drafting structured issue proposals that include titles, user stories, descriptions, and project-specific terminology ready for tracker publication.

What is the best way to plan software development issues using vertical slices?▼

The best way to plan software development issues using vertical slices is to map complete user-facing paths as tracer-bullet issues, creating a dependency-aware breakdown that teams can independently grab for implementation.

Does issue planning with vertical slices work for technical proposals?▼

Issue planning with vertical slices works for technical proposals by breaking them into independently executable deliverable slices, applying structured issue drafting with dependencies and acceptance criteria to organize implementation work.

Do I need a structured product plan to create a dependency-aware issue breakdown?▼

Yes, you need a structured product plan, specification, or PRD to create a dependency-aware issue breakdown, as the decomposition process requires defined feature parameters to draft actionable issues with accurate acceptance criteria.