PRDs & requirements
The product-context layer above issues. A project has a single Goal document plus any number of PRDs — each a versioned markdown body that parents structured Requirement rows.
Goal documents
Section titled “Goal documents”The goal doc answers why the project exists. At dispatch it lands first in the synthesized agent preamble, before designs and guidelines.
A PRD is a versioned markdown document describing a slice of product intent. Requirements are the child rows Halyard traces from PRD all the way to a PR and test path — see Traceability & compliance.
Requirements
Section titled “Requirements”Requirements are the unit of traceability. Each carries a definition of ready, a definition of done, and a testing plan that flows into the agent’s task context.