to-issues

Convert project plans into verifiable vertical-slice GitHub issues with acceptance criteria.

Updated May 3, 2026
One-click install
npx skills add https://github.com/druejaramillo/skills --skill to-issues-druejaramillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/druejaramillo/skills/tree/main/project/to-issues
Command: npx skills add https://github.com/druejaramillo/skills --skill to-issues-druejaramillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of translating high-level project plans, PRDs, or decision records into granular, actionable development tasks without losing context or creating poorly defined work.

Core Features & Use Cases

  • Vertical Slice Generation: Automatically breaks down complex requirements into tracer-bullet issues that deliver end-to-end value.
  • Expand-Migrate-Contract Pattern: Safely manages broad mechanical changes across interfaces to ensure system stability.
  • Dependency Mapping: Identifies and sequences tasks to ensure an acyclic, logical implementation flow.
  • Use Case: Use this when you have a finalized product specification and need to generate a set of GitHub issues that are ready for engineering implementation.

Quick Start

Use the to-issues skill to break the current project plan into a set of independent vertical-slice tickets.

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 product requirements into actionable tickets?

To break down product requirements into actionable tickets, you convert high-level plans into independent, verifiable vertical-slice implementation tickets. This analyzes existing documentation to define observable outcomes, acceptance criteria, and dependency relationships.

What is the expand-migrate-contract pattern for software architecture changes?

The expand-migrate-contract pattern safely manages broad mechanical changes across interfaces to ensure system stability. It enforces system compatibility and verifiable progress during complex architectural migrations.

How do I generate vertical slices from a high-level project plan?

Generating vertical slices from a high-level project plan involves breaking down complex requirements into tracer-bullet issues that deliver end-to-end value. This ensures each implementation ticket is independent and observable.

Can I map task dependencies when converting PRDs to development issues?

Yes, you can map task dependencies when converting PRDs to development issues. The process identifies and sequences tasks to ensure an acyclic, logical implementation flow throughout the project lifecycle.

What's the best way to create tracer-bullet issues for agile development?

The best way to create tracer-bullet issues for agile development is by analyzing finalized product specifications to define observable outcomes and acceptance criteria. This automatically breaks down complex requirements into end-to-end value delivery.