PRD Generation

PRD Generation

After you upload documents and trigger generation, SpecGraph's AI reads everything you've provided and produces a structured Product Requirements Document (PRD). This is the foundation that all departments will review and respond to via their surveys.

What the AI Generates

The AI produces a multi-section PRD tailored to your project type and the content of your documents. A typical PRD includes sections such as:

• Project Overview — a summary of the project, its purpose, and its scope.
• Goals & Success Metrics — what the project should achieve and how success will be measured.
• User Personas — the types of users the product is designed for.
• Functional Requirements — what the product must do, broken into features and user stories.
• Non-Functional Requirements — performance, security, scalability, and reliability expectations.
• Technical Constraints — platform requirements, integration needs, or architectural decisions.
• Out of Scope — explicit list of things this project does not cover.

The exact sections generated depend on the template you chose during project creation.

Reviewing the Generated PRD

Once generation is complete, navigate to the PRD page of your project. You'll see each section rendered as a card with the AI-generated content.

Take time to read through each section carefully. Ask yourself:

• Is the problem statement accurate?
• Are the user personas realistic?
• Do the functional requirements capture the right scope?
• Are there any obvious gaps or misinterpretations?

This is your opportunity to course-correct before opening surveys. Departments will read this PRD as context for their surveys, so it should be a reasonable starting point even if it's not perfect.

Guided Questions

Alongside each PRD section, the AI generates guided questions — structured prompts that help departments think through their requirements in the context of that section. For example, under a "Security Requirements" section, the AI might generate questions like:

• "Does your department handle personally identifiable information (PII) in this workflow?"
• "Are there specific compliance frameworks (SOC 2, HIPAA, GDPR) that apply to your team?"

These questions appear in each department's survey and are designed to elicit specific, actionable wishes rather than vague responses.

PRD Comments

You and your team can add comments to any PRD section directly from the PRD page. Comments are visible to everyone with access to the project and are useful for flagging areas of concern before surveys open, or annotating sections that need clarification.

Understanding Wish Counts

Once surveys begin and departments submit wishes, each PRD section shows a badge with the number of wishes tied to it. This helps you quickly identify which parts of the PRD are generating the most interest or concern from departments.

The PRD Is a Starting Point

It's important to understand that the AI-generated PRD is not the final document — it's a starting point for collaborative refinement. Its purpose is to:

1. Give all departments a shared frame of reference before they submit their requirements.
2. Ensure the AI has something concrete to compare wishes against during conflict detection.
3. Provide structure that the unification step will build upon.

You do not need the PRD to be perfect before opening surveys. Departments will add, amend, and push back on it through their wishes.

Opening Surveys

When you're ready to move forward, navigate to the Surveys page and click Open Surveys. This creates individual surveys for each department and advances the project to the Surveying phase. See Collecting Wishes for what happens next.