workflows added to sub items in plan project phase. updated single action checks to be ifs on the action.

This commit is contained in:
Brian Madison
2025-10-05 11:32:45 -05:00
parent aefe72fd60
commit 33d893bef2
26 changed files with 935 additions and 404 deletions

View File

@@ -15,18 +15,19 @@
<action>Load project-workflow-analysis.md</action>
<action>Confirm Level 3-4 - Full product or platform</action>
<check>If continuation_mode == true:</check>
<action>Load existing PRD.md and check completion status</action>
<ask>Found existing work. Would you like to:
<check if="continuation_mode == true">
<action>Load existing PRD.md and check completion status</action>
<ask>Found existing work. Would you like to:
1. Review what's done and continue
2. Modify existing sections
3. Start fresh
</ask>
<action>If continuing, skip to first incomplete section</action>
</check>
<check>If new or starting fresh:</check>
Check `output_folder` for `product_brief`, `market_research`, and other docs.
<check if="new or starting fresh">
Check `output_folder` for `product_brief`, `market_research`, and other docs.
<critical>For Level 3-4, Product Brief is STRONGLY recommended</critical>
@@ -35,6 +36,7 @@ Check `output_folder` for `product_brief`, `market_research`, and other docs.
Get comprehensive description of the project vision.
<template-output>description</template-output>
</check>
</step>
@@ -200,15 +202,10 @@ Since this is a Level {{project_level}} project, you need architecture before st
- Input: PRD.md, epics.md
- Output: architecture.md
<check>If project has significant UX/UI components (Level 3-4 typically does):</check>
<check 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
- [ ] **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
</check>
### Phase 2: Detailed Planning
@@ -246,7 +243,7 @@ Since this is a Level {{project_level}} project, you need architecture before st
<ask>Project Planning Complete! Next immediate action:
1. Start architecture workflow
1. Start architecture workflow with the architect in a new context window
2. Create UX specification (if UI-heavy project)
3. Generate AI Frontend Prompt (if UX complete)
4. Review all outputs with stakeholders
@@ -255,12 +252,14 @@ Since this is a Level {{project_level}} project, you need architecture before st
Which would you like to proceed with?</ask>
<check>If user selects option 2:</check>
<action>LOAD: {installed_path}/ux/instructions-ux.md</action>
<action>Pass mode="integrated" with Level 3-4 context</action>
<check if="user selects option 2">
<invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan/ux/workflow.yaml</invoke-workflow>
<action>Pass mode="integrated" with Level 3-4 context</action>
</check>
<check>If user selects option 3:</check>
<invoke-task>{project-root}/bmad/bmm/tasks/ai-fe-prompt.md</invoke-task>
<check if="user selects option 3">
<invoke-task>{project-root}/bmad/bmm/tasks/ai-fe-prompt.md</invoke-task>
</check>
</step>

View File

@@ -15,24 +15,25 @@
<action>Load project-workflow-analysis.md</action>
<action>Confirm Level 1-2 - Feature or small system</action>
<check>If continuation_mode == true:</check>
<action>Load existing PRD.md and check completion status</action>
<ask>Found existing work. Would you like to:
<check if="continuation_mode == true">
<action>Load existing PRD.md and check completion status</action>
<ask>Found existing work. Would you like to:
1. Review what's done and continue
2. Modify existing sections
3. Start fresh
</ask>
<action>If continuing, skip to first incomplete section</action>
</check>
<check>If new or starting fresh:</check>
Check `output_folder` for existing docs. Ask user if they have a Product Brief.
<check if="new or starting fresh">
Check `output_folder` for existing docs. Ask user if they have a Product Brief.
<action>Load prd_template from workflow.yaml</action>
<critical>Get the core idea of what they're building</critical>
<critical>Discuss with them to get the core idea of what they're building</critical>
<template-output>description</template-output>
</check>
</step>
@@ -155,13 +156,15 @@ Only document ACTUAL assumptions from discussion.
Run cohesion validation? (y/n)</ask>
<check>If yes:</check>
<action>Load {installed_path}/checklist.md</action>
<action>Review all outputs against "Cohesion Validation (All Levels)" section</action>
<action>Validate PRD sections, then cohesion sections A-H as applicable</action>
<action>Apply Section B (Greenfield) or Section C (Brownfield) based on field_type</action>
<action>Include Section E (UI/UX) if UI components exist</action>
<action>Generate comprehensive validation report with findings</action>
<check if="yes">
<action>Load {installed_path}/checklist.md</action>
<action>Review all outputs against "Cohesion Validation (All Levels)" section</action>
<action>Validate PRD sections, then cohesion sections A-H as applicable</action>
<action>Apply Section B (Greenfield) or Section C (Brownfield) based on field_type</action>
<action>Include Section E (UI/UX) if UI components exist</action>
<action>Generate comprehensive validation report with findings</action>
</check>
</step>
@@ -194,15 +197,10 @@ Since this is a Level {{project_level}} project, you need solutioning before imp
- Input: PRD.md, epic-stories.md
- Output: solution-architecture.md, tech-spec-epic-N.md files
<check>If project has significant UX/UI components (Level 1-2 with UI):</check>
<check if="project has significant UX/UI components (Level 1-2 with UI)">
- [ ] **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, epic-stories.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
- [ ] **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, epic-stories.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
</check>
### Phase 2: Detailed Planning
@@ -239,12 +237,16 @@ Since this is a Level {{project_level}} project, you need solutioning before imp
Which would you like to proceed with?</ask>
<check>If user selects option 2:</check>
<action>LOAD: {installed_path}/ux/instructions-ux.md</action>
<action>Pass mode="integrated" with Level 1-2 context</action>
<check if="user selects option 2">
<invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan/ux/workflow.yaml</invoke-workflow>
<action>Pass mode="integrated" with Level 1-2 context</action>
<check>If user selects option 3:</check>
<invoke-task>{project-root}/bmad/bmm/tasks/ai-fe-prompt.md</invoke-task>
</check>
<check if="user selects option 3">
<invoke-task>{project-root}/bmad/bmm/tasks/ai-fe-prompt.md</invoke-task>
</check>
</step>

View File

@@ -0,0 +1,95 @@
# Product Requirements Document (PRD) Workflow
name: prd
description: "Scale-adaptive PRD workflow for project levels 1-4. Level 1-2: focused PRD + solutioning handoff. Level 3-4: full PRD with epics + architect handoff. Automatically adjusts scope based on project complexity."
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
project_name: "{config_source}:project_name"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/2-plan/prd"
# Instructions - routes to appropriate level-based instructions
instructions_med: "{installed_path}/instructions-med.md" # Level 1-2
instructions_lg: "{installed_path}/instructions-lg.md" # Level 3-4
# Templates
prd_template: "{installed_path}/prd-template.md"
analysis_template: "{installed_path}/analysis-template.md"
epics_template: "{installed_path}/epics-template.md"
# Output configuration
analysis_file: "{output_folder}/project-workflow-analysis.md"
default_output_file: "{output_folder}/PRD.md"
epics_output_file: "{output_folder}/epics.md"
validation_output_file: "{output_folder}/PRD-validation-report.md"
# Recommended input documents
recommended_inputs:
- product_brief: "{output_folder}/product-brief.md"
- market_research: "{output_folder}/market-research.md"
# Scale parameters - adaptive by project level
scale_parameters:
level_1: "1-10 stories, 1 epic, minimal PRD + solutioning handoff"
level_2: "5-15 stories, 1-2 epics, focused PRD + solutioning handoff"
level_3: "12-40 stories, 2-5 epics, full PRD + architect handoff"
level_4: "40+ stories, 5+ epics, enterprise PRD + architect handoff"
# Claude Code integration points
claude_code_enhancements:
- injection_point: "prd-subagents"
- available_subagents:
- requirements-analyst: "Requirements analysis and refinement"
- user-journey-mapper: "User journey and epic boundaries"
- epic-optimizer: "Epic scope optimization"
- document-reviewer: "PRD quality validation"
# Workflow configuration
interactive: true # User checkpoints throughout
autonomous: false # Requires user input
allow_parallel: false # Sequential planning process
# Product frameworks available
frameworks:
- "Jobs-to-be-Done"
- "User Story Mapping"
- "Epic Decomposition"
- "Acceptance Criteria"
- "MoSCoW Prioritization"
web_bundle:
name: "prd"
description: "Scale-adaptive PRD workflow for project levels 1-4. Level 1-2: focused PRD + solutioning handoff. Level 3-4: full PRD with epics + architect handoff. Automatically adjusts scope based on project complexity."
author: "BMad"
# Note: Router workflow will load appropriate instructions based on level
instructions_med: "bmad/bmm/workflows/2-plan/prd/instructions-med.md"
instructions_lg: "bmad/bmm/workflows/2-plan/prd/instructions-lg.md"
use_advanced_elicitation: true
web_bundle_files:
- "bmad/bmm/workflows/2-plan/prd/instructions-med.md"
- "bmad/bmm/workflows/2-plan/prd/instructions-lg.md"
- "bmad/bmm/workflows/2-plan/prd/prd-template.md"
- "bmad/bmm/workflows/2-plan/prd/analysis-template.md"
- "bmad/bmm/workflows/2-plan/prd/epics-template.md"
# Scale parameters - adaptive by project level
scale_parameters:
level_1: "1-10 stories, 1 epic, minimal PRD + solutioning handoff"
level_2: "5-15 stories, 1-2 epics, focused PRD + solutioning handoff"
level_3: "12-40 stories, 2-5 epics, full PRD + architect handoff"
level_4: "40+ stories, 5+ epics, enterprise PRD + architect handoff"
# Product frameworks available
frameworks:
- "Jobs-to-be-Done"
- "User Story Mapping"
- "Epic Decomposition"
- "Acceptance Criteria"
- "MoSCoW Prioritization"
# Workflow configuration
interactive: true # User checkpoints throughout
autonomous: false # Requires user input
allow_parallel: false # Sequential planning process