Can AI draft PRDs, spec docs, and project charters?

Grounded in precedent, not generic templates

Most AI spec-writing tools produce generic documents because they reason from training data, not from your organization. bRRAIn's Write Spec skill does the opposite. It reads your past PRDs, past decisions, and current constraints from the POPE graph and drafts a new document that matches how your team writes. Terminology stays consistent, structure matches precedent, and cited decisions link back to the actual rows in Key-Decisions.md. The output reads like something your senior PM wrote, because it was trained on the senior PM's prior output.

What the skill reads

When a PM invokes the Write Spec skill, the Handler pulls four inputs: the three most similar past PRDs by tag overlap, the relevant decisions that touched the affected modules, the current charter for the active project, and any in-scope constraints from NextSteps.md. The Consolidator merges these into a grounded context block the model reasons from. The draft cites each major claim to its source in the workspace, so the PM reviewing it can click a line and see whether the cited decision actually supports the claim.

The agent does not invent

"The agent does not invent" is a product discipline, not a wish. bRRAIn enforces it through grounding: if the skill cannot trace a claim back to a graph node, the claim is omitted rather than generated. That means early drafts are sometimes thinner than the PM wants. The PM fills the gaps — and those gaps get captured back into the graph for the next draft. Over a quarter, the team's spec-writing speed doubles, not because the agent is smarter, but because the precedent base keeps getting richer. The POPE graph compounds.

PM workflow around the skill

A PM running Write Spec opens a new page in the workspace, types a one-paragraph problem statement, and invokes the skill. Thirty seconds later a structured draft appears with sections for goals, non-goals, users, constraints, open questions, and success criteria. The PM edits inline. When the draft is solid, the PM marks it "ratified"; the Control Plane records the approval, and the new PRD becomes precedent for the next draft. Book a demo to watch a PRD land in under a minute.

Relevant bRRAIn products and services

• Handler — runs the Write Spec skill and grounds every draft in your actual precedent.
• POPE Graph RAG — the precedent layer that compounds as each ratified PRD joins it.
• Consolidator — merges past PRDs, decisions, and constraints into the grounded context the draft reads from.
• bRRAIn Workspaces — where the draft lands, where the PM edits, where ratified specs become precedent.
• Control Plane — records the PM's ratification so the new PRD becomes canonical precedent for the next draft.