Back to marketplace

PRD to Vertical Slice Issues

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

Engineeringp4
by AgentVoltv1.0.0Published 1y ago1 install
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Break down this product roadmap into implementation issues”
Beforegeneric AI agent
Breaking down a roadmap into issues is smart for parallel work. I'd need to see the roadmap and understand your development flow—how do you define vertical slices? Are you aiming for tracer-bullet architectures that touch every layer, or smaller incremental steps? How granular should each issue be, and do you have a preference for which parts to tackle first? I can help you draft issues with blocking relationships, but knowing your team's velocity and testing conventions would help prioritize them.
Afterwith PRD to Vertical Slice Issues
VERTICAL SLICE BREAKDOWN: ROADMAP → ISSUES

PARENT EPIC
Title → "Build Real-time Collaboration" (PRD link)
Status → Ready for slicing
Estimated total → 40-50 hours across 5 slices

VERTICAL SLICE 1: FOUNDATION
Title → "Event stream schema and API contract"
Type → Tracer bullet (touches schema, API, client)
Blocked by → Nothing
Blocks → Slices 2, 3, 4, 5
Estimate → 8 hours (design 3h, implement 4h, test 1h)
Owner → Backend lead
Checklist → Schema designed, API endpoint live, docs written
Risk → Schema changes downstream (mitigate with contract tests)

VERTICAL SLICE 2: WEBSOCKET PLUMBING
Title → "Upgrade to WebSocket from polling"
Blocked by → Slice 1 (API contract)
Blocks → Slices 4, 5
Estimate → 6 hours
Owner → Backend + DevOps
Testing → Load test (100 concurrent), no regression on HTTP routes

VERTICAL SLICE 3: CLIENT SYNC STATE
Title → "Sync local state with server events"
Blocked by → Slice 1 (event schema)
Blocks → Slice 5 (UI)
Estimate → 7 hours
Owner → Frontend lead
Testing → 10 edge cases (reorder, delete during sync, offline)

VERTICAL SLICE 4: REAL-TIME UI UPDATES
Title → "Render state changes as server events arrive"
Blocked by → Slices 2, 3
Blocks → Nothing
Estimate → 9 hours
Owner → Frontend
Testing → Concurrent edits, no race conditions

VERTICAL SLICE 5: E2E FLOW & INTEGRATION
Title → "End-to-end collaboration scenario (2 users editing)"
Blocked by → Slices 1, 3, 4
Blocks → Nothing (release gate)
Estimate → 8 hours
Owner → QA + Full-stack review
Testing → Record video of 2-user scenario, edge case checklist

DEPENDENCY GRAPH
Parallel work possible → Slices 2 & 3 can start after Slice 1 complete
Critical path → 1 → 2 → 4 → 5 (30 hours)
Non-blocking → Slice 3 can finish independently

SUGGESTED SPRINT ALLOCATION
Week 1 → Slice 1 (foundation)
Week 2 → Slices 2 & 3 (parallel)
Week 3 → Slices 4 & 5 (sequential due to blocking)

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.

SKILL.md preview

SKILL.md
---
name: prd-to-vertical-slices
description: Use this skill when a PRD needs to be broken into small vertical-slice GitHub issues with explicit blocking relationships so agents or engineers can parallelize the work.
version: 1.0.0
category: Engineering
author: AgentVolt
license: proprietary
tags:
  - engineering
  - p4
---

# PRD to Vertical Slice Issues

Converts a PRD into a real work queue: tracer-bullet slices filed as issues with blocking links, so work can be pulled in parallel.

## When to use

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill