BMAD-METHOD/bmad/bmm/workflows/2-plan/prd/instructions-lg.md

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 project-workflow-analysis.md Confirm Level 3-4 - Full product or platform

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

1. Review what's done and continue
2. Modify existing sections
3. Start fresh If continuing, skip to first incomplete section

If new or starting fresh: 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.

description

What is the deployment intent?

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

deployment_intent

Goal Guidelines:

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

Each goal should be measurable and outcome-focused.

goals

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

context

FR Guidelines:

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

Group related features logically.

functional_requirements

Match NFRs to deployment intent (8-12 NFRs)

non_functional_requirements

Journey Requirements:

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

Map complete user flows with decision points.

user_journeys

8-10 UX principles guiding all interface decisions.

ux_principles

Epic Guidelines:

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

Each epic delivers significant value.

epics

Load epics_template from workflow.yaml

Create separate epics.md with full story hierarchy

epic_overview

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)

epic_{{epic_number}}_details

List features/ideas preserved for future phases.

out_of_scope

Only document ACTUAL assumptions from discussion.

assumptions_and_dependencies

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:

1. This PRD: {{default_output_file}}
2. Epic structure: {{epics_output_file}}
3. Input documents: {{input_documents}}

Ask architect to:

• Run architecture workflow
• Consider reference architectures
• Generate solution fragments
• Create 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: architecture.md

If project has significant UX/UI components (Level 3-4 typically does):

• 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, 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

Phase 2: Detailed Planning

• Generate detailed user stories

  • Command: workflow generate-stories
  • Input: epics.md + 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:

1. Start architecture workflow
2. Create UX specification (if UI-heavy project)
3. Generate AI Frontend Prompt (if UX complete)
4. Review all outputs with stakeholders
5. Begin detailed story generation
6. Exit workflow

Which would you like to proceed with?

If user selects option 2: LOAD: {installed_path}/ux/instructions-ux.md Pass mode="integrated" with Level 3-4 context

If user selects option 3: {project-root}/bmad/bmm/tasks/ai-fe-prompt.md