/prd-to-issues

Break a PRD or plan into independently-grabbable issues using vertical slices (tracer bullets), then file each as a local Markdown work order in issues/. The output is designed to be consumed by a ralph loop — an agent that picks the next eligible issue, implements it, and moves it to issues/done/, one iteration at a time.

Issues are work orders, not archival docs

A PRD is durable and abstract on purpose. Issues are the opposite: ephemeral, concrete work orders consumed once by the loop and then retired. A fresh-context agent picking up an issue has no memory of this conversation — so be concrete:

• Name the modules, files, and existing patterns the agent should touch or copy. Stale pointers are fine; the issue is discarded the moment it's done.
• Reference the PRD for why and for the broader context; tell the issue where and what.
• Over-abstracting an issue "for durability" is the main way it becomes unexecutable. Don't.

Workflow

You may skip steps the conversation already covered — capture, don't re-interview.

1. Locate the PRD or plan

The source is a local Markdown file (or content already in your context).