The workspace

PRDs

A PRD is a short spec the product manager writes before the team builds anything big. The prds tab is where you read and approve them.

Why PRDs exist

Small requests go straight to a ticket. But for anything with real scope, a redesign, a new feature area, the PM first writes down what will be built, for whom, and what's out of scope. This is the cheapest moment to catch a misunderstanding: changing a sentence in a spec costs nothing, changing built code costs a rework cycle.

Reviewing a PRD

When a PRD is ready you get an action card in chat and the document shows up in this tab. Read it like a plan from a contractor. Comment on anything that's off: click into the doc, add a comment, and the PM responds in a thread right on the document. Comments can be resolved as they're addressed, and you can show or hide resolved ones to see what's still open.

Approve or reject

• Approve: the PM decomposes the PRD into tickets and the team starts building.
• Reject: you have to give a reason, and that reason goes back to the PM in the original thread. A rejection with a clear reason usually comes back as a much better second draft.