prd-to-issues

Read the PRD to understand the problem, user flows, constraints, and riskiest areas, then split the work into vertical slices that are end-to-end and independently validatable. Write each slice as an issue file with goal, scope, out-of-scope, implementation notes, validation, and dependencies.

Tracer-bullet vertical slices are thin end-to-end increments of functionality that exercise real user value early and reduce uncertainty quickly. They contrast with horizontal phases that split work by layer such as backend, frontend, and database, which delay visible progress.

Issue files are written under .prd/<prd-slug>/issues/ with ordered filenames like 01-<slice-slug>.md and 02-<slice-slug>.md. The issues directory is created if it does not exist, and the PRD slug is inferred from the PRD artifact if not given explicitly.

Avoid layer-based splitting when it produces disconnected infrastructure work with no independently validatable outcome. Only split by layer when that is genuinely the safest shape; otherwise prefer end-to-end slices that leave the system in a coherent state.

Issues are ordered so early slices reduce the most important uncertainty and later slices build on proven capability. Explicit dependencies are called out only when necessary, keeping each issue independently understandable without rereading the full PRD.