Skill

prd-to-issues

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

npx claudepluginhub qhuang20/shazam --plugin shazam

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets).

SKILL.md

Similar Skills

to-issues

Decomposes plans, PRDs, or specs into vertical-slice issues as markdown files or GitHub issues. Creates independently demoable end-to-end tasks across layers for parallel implementation.

odin

to-issues

47.6k

Breaks plans, specs, or PRDs into thin vertical-slice issues on the project issue tracker using tracer bullets. Useful for converting plans into approved, grabbable tickets.

mattpocock-skills

slice

Breaks grill-session outputs, plans, or PRDs into parent GitHub story issue with synthesized PRD body and thin tracer-bullet vertical-slice child issues on sonthanh/ai-brain repo, with Parent/Blocked-by links and HITL/AFK marking. Useful for converting alignment to demoable tickets.

2 files

brain-os

Stats

Stars2

Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

PRD to Issues

Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets).

Process

1. Locate the PRD

Ask the user for the PRD GitHub issue number (or URL).

If the PRD is not already in your context window, fetch it with gh issue view <number> (with comments).

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code.

3. Draft vertical slices

Break the PRD into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

Title: short descriptive name
Type: HITL / AFK
Blocked by: which other slices (if any) must complete first
User stories covered: which user stories from the PRD this addresses

Ask the user:

Does the granularity feel right? (too coarse / too fine)
Are the dependency relationships correct?
Should any slices be merged or split further?
Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

5. Create the GitHub issues

For each approved slice, create a GitHub issue using gh issue create. Use the issue body template below.

Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.

## Parent PRD

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Reference specific sections of the parent PRD rather than duplicating content.

Acceptance criteria

Criterion 1
Criterion 2
Criterion 3

Blocked by

Blocked by # (if any)

Or "None - can start immediately" if no blockers.

User stories addressed

Reference by number from the parent PRD:

User story 3
User story 7

Do NOT close or modify the parent PRD issue.

What comes next

After issues are created, suggest: "Issues created! Start coding, or /grill-me on any issue that feels underspecified."