Writing PRDs

A PRD is the input contract for the planning phase. A good PRD lets a planning agent produce a usable plan in one shot instead of burning turns asking "what did you mean by X?". A bad PRD causes planner thrash, review rejection, and verification failures downstream.

This skill is platform-agnostic. It assumes a plan → review → verify → ship flow where a PRD is written first, a planner decomposes it into steps, and a verifier checks the result against the PRD's acceptance criteria. Adapt the storage and field mechanics below to whatever tracker you use.

Storage Location

Prefer making the tracker issue body the PRD. One document per work item, one location: the body of an issue in the project's tracker. Avoid scattering PRDs across local sidecar files that drift out of sync the moment work starts.