skills.rest
henrycashe26
henrycashe26COMMUNITY
Explore all skills by this author →
GitHub

to-issues

Break project plans and PRDs into vertical slice issues with acceptance criteria.

Updated Apr 13, 2026
Search Tags:#workflow#planning#github#issue-tracking#project-management#vertical-slicing
One-click install
npx skills add https://github.com/henrycashe26/my_skills --skill to-issues-henrycashe26
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/henrycashe26/my_skills/tree/main/coding/to-issues
Command: npx skills add https://github.com/henrycashe26/my_skills --skill to-issues-henrycashe26

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of translating high-level project plans, PRDs, or specifications into granular, actionable tasks, ensuring that work is broken down into manageable, independently-grabbable units.

Core Features & Use Cases

  • Vertical Slicing: Automatically breaks complex requirements into tracer-bullet vertical slices that cut through all integration layers.
  • Triage Integration: Standardizes issue creation by applying appropriate triage labels and dependency tracking.
  • Use Case: When you have a complex feature specification, use this skill to generate a list of implementation tickets that are ready for development, complete with acceptance criteria and dependency mapping.

Quick Start

Use the to-issues skill to break the current project plan into a set of actionable 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 project plan into actionable GitHub issues?▼

Vertical slicing decomposes complex requirements into tracer-bullet slices cutting through all integration layers, ensuring work is broken down into manageable, independently-grabbable units for structured ticket creation.

What is the best way to create vertical slice issues from a PRD?▼

Creating vertical slice issues from a PRD requires applying tracer-bullet development principles to generate implementation tickets cutting through integration layers, complete with clear acceptance criteria and standardized triage labels.

Can I use this to manage dependencies and triage labels for issue tracking?▼

Yes, you can manage dependencies and triage labels for issue tracking. The process standardizes issue creation by applying appropriate triage labels and dependency tracking across generated tickets.

Does this issue decomposition approach work for tracer-bullet development workflows?▼

Yes, this issue decomposition approach works for tracer-bullet development workflows. It explicitly satisfies tracer-bullet requirements by generating vertical slices that cut through all integration layers.

How do I ensure generated issue tickets are independently-grabbable by developers?▼

You ensure generated issue tickets are independently-grabbable by breaking complex specifications into vertical slices with clear acceptance criteria and dependency mapping, preventing overlapping work.

Related Skills

Explore More Software Engineering Skills→
yash-gargyash-garg

to-issues

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

Community
Intermediate
tonombtonomb

to-tickets

Decompose project plans into dependency-mapped tracer-bullet tickets.

Community
Advanced
NourcineAbNourcineAb

github-project-management

Automate GitHub issue tracking, board synchronization, and sprint planning workflows.

Community
Advanced
ayehiaaayehiaa

tdd

Apply test-driven development through red-green-refactor cycles with behavior-focused integration tests.

Community
Intermediate