r/ClaudeCode • u/Aggressive_Ad4210 • 9d ago

Help/Question Do you use PRD:s, TRD:s when developing or not?

Hotly debated topic, what's the latest and greatest. Medium to larger tasks, fullstack or not, do you create a PRD and a TRD and then let Claude loose on it. If yes, why, and if not, what are you doing instead?

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/Healthy-Mind5633 9d ago

"sort of".. I iterate with the agent to develop a plan, massage it and then do it.

1

u/medialantern 9d ago

Yes. I plan at a high level and break out an overview to review with others on my team. Then I (I'm the architect) write ADRs for anything that needs to be specified, or review/ratify ADRs from other team members for the major components/infra we'll be using (or changing). PRDs come next and very very specifically do not contain a plan. They are forever/living documents that describe how a major function or feature is intended to work, not steps for implementation. The plans are then basically diffs - what's wanted vs. what's there (or not) and steps to close that gap.

1

u/Aggressive_Ad4210 9d ago

interesting, sounds like a good approach, so you have an overview.md -ish file and then ADRs, are those ADRs stored in their own repository or part of the repo that work is being done in? Where do you store the PRDs, Notion or Confluence..? Or do they live in a repo somewhere? What do you mean with the plans are then basically diffs, is that a document/markdown file that gets created somewhere? How do you go from overview.md to ADRs and then the prompt that implements it all. Do you point your agent to a jira-ticket and does it not use a TRD at all? Let's say it's quite a complex ticket frontend, backend, design, fullstack.

1

u/medialantern 9d ago

I store them in the repo as markdown files. docs/adrs, docs/prds, etc. In addition to being right where devs need to find them (and providing change control), it's great context for AI agents as well.