issues

Converts high-level plans and PRDs into executable implementation tasks.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill issues-hschne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/hschne/pi-stuff/tree/main/skills/issues
Command: npx skills add https://github.com/hschne/pi-stuff --skill issues-hschne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured plans, specs, PRDs, or parent issues often leave development teams unsure how to split work into independent, executable tasks, leading to misaligned priorities, blocked workstreams, and wasted effort on poorly defined work items.

Core Features & Use Cases

  • Vertical Slice Work Breakdown: Splits high-level work into tracer-bullet vertical slices, where each slice delivers a complete, demoable user behavior end-to-end rather than isolated technical layers.
  • Standardized Issue Definition: Enforces a consistent structure for each issue, including clear titles, acceptance criteria, and dependency tracking, to eliminate ambiguity for developers or autonomous agents picking up work.
  • Use Case Example: A product team with a new password reset feature PRD can use this skill to split the work into 4 small, testable slices that can be worked on in parallel without blocking each other, with clear acceptance criteria for each slice.

Quick Start

Use the issues skill to break down the attached new checkout flow PRD into 5 independent vertical slice issues with clear acceptance criteria and dependency links for each.

Frequently Asked Questions about issues

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

FAQPage Schema
How do I break down a PRD into executable development issues?

To break down a PRD into executable development issues, you convert high-level plans into discrete, independently executable implementation tasks. This creates well-defined, demoable vertical slices with clear acceptance criteria and structured dependency tracking for developers.

What is vertical slice work breakdown for agile projects?

Vertical slice work breakdown splits high-level work into tracer-bullet vertical slices, where each slice delivers a complete, demoable user behavior end-to-end rather than isolated technical layers. This enables parallel execution by developers or autonomous agents across any issue tracking platform.

How do I split parent issues into independent tasks for parallel execution?

Splitting parent issues into independent tasks involves breaking plans into tracer-bullet vertical slices with clear acceptance criteria and dependency links. This standardized issue definition eliminates ambiguity and unblocks workstreams, allowing developers or autonomous agents to work in parallel without blocking each other.

Do I need a specific issue tracking platform to generate vertical slice tickets?

No specific issue tracking platform is required to generate vertical slice tickets. The breakdown process produces well-defined, demoable slices aligned with project domain vocabulary that can be exported and used across any issue tracking platform.

What's the best way to structure acceptance criteria for work breakdown issues?

The best way to structure acceptance criteria for work breakdown issues is to enforce a consistent structure for each issue, including clear titles and dependency tracking. This ensures each vertical slice delivers a complete, testable user behavior end-to-end, reducing rework.

Why should I use tracer-bullet vertical slices instead of technical layer tasks?

Tracer-bullet vertical slices deliver a complete, demoable user behavior end-to-end rather than isolated technical layers. This approach to work breakdown reduces misaligned priorities, prevents blocked workstreams, and minimizes wasted effort on poorly defined work items.