PRD Writer

A PRD is the input contract for the planning phase. It must contain enough context, acceptance criteria, scope boundaries, and verification detail for a planning agent to produce a plan without re-eliciting requirements.

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

Use the tracker issue body as the default PRD location: one document per work item, one location. Avoid local sidecar files unless the repo explicitly uses them as source truth.