# Prd To Issues

> Break a PRD into independently-grabbable beans 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.

- Skill: `franky47/prd-to-issues` (Agent Skill)
- Install (CLI): `npx skillmds@latest add franky47/prd-to-issues`
- Raw SKILL.md: https://api.skillmd.com/api/skills/franky47/prd-to-issues/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: franky47 (https://skillmd.com/u/franky47)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/franky47/prd-to-issues

---


# PRD to Issues

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

## Process

### 1. Locate the PRD

Ask the user for the PRD beans issue ID.

If the PRD is not already in your context window, fetch it with `beans show <id>`.

### 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.

<vertical-slice-rules>
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests, docs)
- Docs ship in the same issue as the code, not as a follow-up
- A completed slice is demoable or verifiable on its own
- Prefer many thin slices over few thick ones
</vertical-slice-rules>

### 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 beans issues

For each approved slice, create a beans issue using `beans create`. Set the type with `--type` (task, feature, bug, etc.), priority with `--priority`, use `--blocked-by <id>` for dependencies, and `--parent <prd-id>` to link each slice back to the parent PRD bean.

**How to create the bean:** do NOT pass the issue body to `beans create` via `-d`/`--body` or stdin — multi-line content breaks. Instead:

1. Run `beans create "<title>" --type <type> --parent <prd-id> [--blocked-by <id>] [--priority <p>]` — metadata only, no body.
2. `beans create` prints the new bean ID. Locate the file with `ls .beans/<id>*` (e.g. `.beans/abc1--<slug>.md`).
3. Use the Edit tool on that file to fill in the body below the frontmatter using the template below.

Create issues in dependency order (blockers first) so you can reference real bean IDs in the `--blocked-by` flag.

<issue-template>
## 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

## User stories addressed

Reference by number from the parent PRD:

- User story 3
- User story 7

</issue-template>

Do NOT archive or modify the parent PRD bean.