Can AI design a system from a PRD?
Yes, if it has design patterns in memory. bRRAIn's graph stores your past ADRs, framework choices, and rejected alternatives. The agent designs from precedent, not generic best practice.
Why ungrounded PRD-to-design fails
Hand a raw LLM a PRD and ask for a system design, and it returns a clean architecture diagram featuring Kafka, Redis, and a CQRS pattern. The design is internally consistent and completely disconnected from your organisation. You already rejected Kafka in 2022, your platform team bans CQRS outside the finance domain, and your Redis deployment has a known capacity ceiling nobody documented publicly. The model does not know any of this. Its design is generic best practice; yours needs to be grounded precedent.
Precedent as the design material
bRRAIn stores your past ADRs, framework choices, and rejected alternatives as nodes in the POPE graph. Each node carries the context that created it: the PRD it responded to, the constraints, the trade-offs, the eventual verdict. When a new PRD arrives, the agent walks the graph to find analogous decisions — "we solved a similar ingestion problem in 2023 with a pull-based model; the rejected push-based alternative failed on auth". The design that emerges is anchored in your history, not in the model's training data.
How the agent writes the design doc
The Handler assembles the prompt with the matched precedent nodes inline and the new PRD alongside. The agent drafts a design doc that cites each choice against an ADR node: "using Postgres per ADR-0027; rejecting DynamoDB per ADR-0031's cost analysis". The Document Portal is where the draft lands for review. Engineers read the doc, confirm or adjust the cited reasoning, and the final version becomes a new ADR in the graph — feeding future designs.
Where human architects still lead
AI design-from-PRD is a first draft, not the architecture. Senior architects review the agent's document, challenge assumptions, and reject choices the agent matched poorly. The architect's role shifts from writing the doc to curating the decisions that power it. Over time, the graph captures enough institutional design thinking that the first draft gets unusually close to the final — because it is built from the same material a senior architect would use mentally. The Platform Architect certification formalises this curation role.
Relevant bRRAIn products and services
- POPE Graph RAG / Memory Engine — stores past ADRs, rejected alternatives, and constraints as design precedent.
- Handler — assembles PRD and matched precedent into a grounded design prompt.
- Document Portal — landing zone for drafted and reviewed design docs.
- Platform Architect certification — formalises the human role of curating design precedent.
- bRRAInDev certification path — the broader developer track covering SDK, integration, and architecture.
- Book a demo — watch a PRD turn into a precedent-cited design draft live.