PRD generator

What CLARA will ask you for

• Programme name — your programme's name (e.g. SKYPROTECT).
• Track — the slice of the programme this artefact belongs to (workstream, capability area, feature line, etc.), or Programme-wide if it spans tracks.
• PRD title — short (e.g. "Incident-report capture v1").
• Inputs — CLARA will search the programme's Confluence space for the problem to build for; problem statement and success criteria; persona for the prd; themes from the research synthesis (optional); original stakeholder ask. You can also paste fresh material if it's not in Confluence yet.

Where the output lands

Knowledge Base/{{track}}/PRDs/{{prd-title}} inside your programme's Confluence space.

Tips

• CLARA asks clarifying questions when inputs are thin. Answer honestly even if it's "I don't know yet" — the Open questions section preserves the unknown.
• Treat CLARA's v0 PRD as a starting position, not a final document. Manual editing after generation is the norm, not the exception.

Before you circulate — self-review checklist

Before sharing the PRD with stakeholders, walk through these checks. Most teams will edit the draft directly to fix gaps; a few questions surface things the draft can't fix on its own.

• Problem statement is one paragraph, framed as a problem (not a solution in disguise). Has a clear "who has the problem."
• Success criteria are measurable and capability-focused — what the capability or product has to be able to do, and to what threshold. No "users will feel more confident" non-criteria.
• Scope table rolls every relevant rank up into a module (or explicitly drops it to Out of scope). No ranked problem is silently unaccounted for; "Out of scope" names the rank and the reason.
• User-story table is ordered by priority, every row's ID · rank ties back to the ranking, and every Evidence cell cites a real verbatim/observation with its source ref. Stories describe outcomes, not features.
• Constraints and dependencies name every external thing the work depends on. Re-read with "what would block this?" in mind.
• Open questions are honest. The first draft is supposed to be wrong in interesting ways; the open questions are where you flag what you don't know.
• Persona references link to specific persona pages — no implicit "the user".