PI

PRD to Vertical Slice Issues

Break a PRD into small vertical-slice GitHub issues with explicit blocking relationships an agent can parallelize.

Engineeringp4matt-pocock
Or just install the prompt above — no subscription needed

About this skill


name: prd-to-vertical-slices description: Break a PRD into small vertical-slice GitHub issues with explicit blocking relationships an agent can parallelize. Use when working on prd to vertical slice issues.

PRD to Vertical Slice Issues

Locates or fetches the parent PRD, drafts tracer-bullet slices that cut through every integration layer, and files each as its own issue that references the parent. Establishes blocked-by links so background agents or Ralph loops can pick up unblocked work in parallel. Use to convert a PRD into a real work queue that agents (or humans) can actually pull from.

What you get

  • 3 to 8 child issues
  • Blocking graph
  • Tracer-bullet ordering
  • Links back to the parent PRD
  • Estimated hours per slice
  • Suggested reviewer per slice

Customize your output

  • PRD issue number: int
  • Max slice count: 3, 5, 8
  • Parallel branches allowed: yes, no
  • Testing convention: unit only, unit plus integration, TDD
  • Agent runner name: manual, background, Ralph
  • Base branch: main, dev

Example output

Four issues: pure function editing engine (blocks nothing), Monaco toggle (blocked by 2), integration wiring (blocked by 1), regression test suite (blocked by all).

Best for

Teams running background or Ralph-loop agents against a queue of issues.


Note: Pairs with architecture-deepening-audit to feed refactor issues into the same pipeline. High confidence.

Source: Ian Nuttall · https://www.youtube.com/watch?v=EJyuu6zlQCg Category: Engineering · Priority: P4

SKILL.md preview

---
name: prd-to-vertical-slices
description: Break a PRD into small vertical-slice GitHub issues with explicit blocking relationships an agent can parallelize. Use when working on prd to vertical slice issues.
---

# PRD to Vertical Slice Issues

Locates or fetches the parent PRD, drafts tracer-bullet slices that cut through every integration layer, and files each as its own issue that references the parent. Establishes blocked-by links so background agents or Ralph loops can pick up unblocked work in parallel. Use to convert a PRD into a real work queue that agents (or humans) can actually pull from.

## What you get

- 3 to 8 child issues
- Blocking graph
- Tracer-bullet ordering
- Links back to the parent PRD
- Estimated hours per slice
- Suggested reviewer per slic...