PRD Workflow - Large Projects (Level 3-4)

The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml This is the LARGE instruction set for Level 3-4 projects - full PRD + architect handoff Project analysis already completed - proceeding with comprehensive requirements NO TECH-SPEC - architecture handled by specialist workflow Uses prd_template for PRD output, epics_template for epics output If users mention technical details, append to technical_preferences with timestamp

Load bmm-workflow-status.md Confirm Level 3-4 - Full product or platform

Load existing PRD.md and check completion status Found existing work. Would you like to:

Review what’s done and continue
Modify existing sections
Start fresh If continuing, skip to first incomplete section

Check output_folder for product_brief, market_research, and other docs.

For Level 3-4, Product Brief is STRONGLY recommended

Load prd_template from workflow.yaml

Get comprehensive description of the project vision.

<template-output>description</template-output>

What is the deployment intent?

MVP for early users
Production SaaS/application
Enterprise system
Platform/ecosystem

<template-output>deployment_intent</template-output>

Goal Guidelines:

Level 3: 3-5 strategic goals
Level 4: 5-7 strategic goals

Each goal should be measurable and outcome-focused.

<template-output>goals</template-output>

1-2 paragraphs on problem, current situation, why now.

<template-output>context</template-output> <invoke-task halt=“true”>{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>

FR Guidelines:

Level 3: 12-20 FRs
Level 4: 20-30 FRs

Group related features logically.

<template-output>functional_requirements</template-output> <invoke-task halt=“true”>{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>

Match NFRs to deployment intent (8-12 NFRs)

<template-output>non_functional_requirements</template-output>

Journey Requirements:

Level 3: 2-3 detailed journeys
Level 4: 3-5 comprehensive journeys

Map complete user flows with decision points.

<template-output>user_journeys</template-output> <invoke-task halt=“true”>{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>

8-10 UX principles guiding all interface decisions.

<template-output>ux_principles</template-output>

Epic Guidelines:

Level 3: 2-5 epics (12-40 stories)
Level 4: 5+ epics (40+ stories)

Each epic delivers significant value.

<template-output>epics</template-output> <invoke-task halt=“true”>{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>

Load epics_template from workflow.yaml

Create separate epics.md with full story hierarchy

<template-output file=“epics.md”>epic_overview</template-output>

<for-each epic=“epic_list”>

Generate Epic {{epic_number}} with expanded goals, capabilities, success criteria.

Generate all stories with:

User story format
Prerequisites
Acceptance criteria (3-8 per story)
Technical notes (high-level only)

<template-output file=“epics.md”>epic_{{epic_number}}_details</template-output> <invoke-task halt=“true”>{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>

</for-each>

List features/ideas preserved for future phases.

<template-output>out_of_scope</template-output>

Only document ACTUAL assumptions from discussion.

<template-output>assumptions_and_dependencies</template-output>

Next Steps for {{project_name}}

Since this is a Level {{project_level}} project, you need architecture before stories.

Start new chat with architect and provide:

This PRD: {{default_output_file}}
Epic structure: {{epics_output_file}}
Input documents: {{input_documents}}

Ask architect to:

Run architecture workflow
Consider reference architectures
Generate solution fragments
Create solution-architecture.md

Complete Next Steps Checklist

Generate comprehensive checklist based on project analysis

Phase 1: Architecture and Design

[ ] Run architecture workflow (REQUIRED)
- Command: workflow architecture
- Input: PRD.md, epics.md
- Output: solution-architecture.md

[ ] Run UX specification workflow (HIGHLY RECOMMENDED for user-facing systems) - Command: workflow plan-project then select “UX specification” - Or continue within this workflow if UI-heavy - Input: PRD.md, epics.md, solution-architecture.md (once available) - Output: ux-specification.md - Optional: AI Frontend Prompt for rapid prototyping - Note: Creates comprehensive UX/UI spec including IA, user flows, components

Update workflow status file to mark ux-spec as next step In status file, set next_action: “Run UX specification workflow” In status file, set next_command: “ux-spec” In status file, set next_agent: “PM” Add to decisions log: “PRD complete. UX workflow required due to UI components.”

Phase 2: Detailed Planning

[ ] Generate detailed user stories
- Command: workflow generate-stories
- Input: epics.md + solution-architecture.md
- Output: user-stories.md with full acceptance criteria
[ ] Create technical design documents
- Database schema
- API specifications
- Integration points
[ ] Define testing strategy
- Unit test approach
- Integration test plan
- UAT criteria

Phase 3: Development Preparation

[ ] Set up development environment
- Repository structure
- CI/CD pipeline
- Development tools
[ ] Create sprint plan
- Story prioritization
- Sprint boundaries
- Resource allocation
[ ] Establish monitoring and metrics
- Success metrics from PRD
- Technical monitoring
- User analytics

Project Planning Complete! Next immediate action:

Start architecture workflow with the architect in a new context window
Create UX specification (if UI-heavy project)
Generate AI Frontend Prompt (if UX complete)
Review all outputs with stakeholders
Begin detailed story generation
Exit workflow

Which would you like to proceed with?

<invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan/ux/workflow.yaml</invoke-workflow> Pass mode=“integrated” with Level 3-4 context

<invoke-task>{project-root}/bmad/bmm/tasks/ai-fe-prompt.md</invoke-task>