plan-project gone, and all level 1-3 workflows are dynamic from the workflow in suggesting what is next

README.md

@@ -188,12 +188,14 @@ The BMM module follows a comprehensive four-phase methodology. Each phase adapts
 - `brainstorm-project` - Generate and refine project concepts
 - `research` - Market research, deep research, prompt generation
 - `product-brief` - Document initial product vision
+- `workflow-init` or `workflow-status` will set up or get the the status of a guided workflow
 
 **Game Designer Agent** _(for game projects)_:
 
 - `brainstorm-game` - Game-specific ideation
 - `game-brief` - Game concept documentation
 - `research` - Game market and technical research
+- `workflow-init` or `workflow-status` will set up or get the the status of a guided workflow
 
 ---
 
@@ -201,18 +203,18 @@ The BMM module follows a comprehensive four-phase methodology. Each phase adapts
 
 **PM Agent**:
 
-- `plan-project` - Creates scale-adaptive PRD or GDD
+- `prd` - Creates scale-adaptive PRD for level 2-4 workflows
 
 The planning workflow adapts to:
 
 - Project complexity (Levels 0-4)
-- Project type (web, mobile, embedded, game, etc.)
+- Project type (web, mobile, embedded, etc.)
 - New vs. existing codebase
 - Team structure
 
 **Game Designer Agent** _(for game projects)_:
 
-- `plan-game` - Uses same workflow but optimized for Game Design Documents
+- `gdd` - Uses a specialized game design document workflow optimized for Game Design Documents
 
 ---
 

src/modules/bmm/README.md

@@ -31,7 +31,7 @@ The heart of BMM - structured workflows for the four development phases:
    - `product-brief` - Product strategy
 
 2. **Planning Phase** (Required)
-   - `plan-project` - Scale-adaptive project planning
+   - `prd` - Scale-adaptive project planning
    - Routes to appropriate documentation based on project complexity
 
 3. **Solutioning Phase** (Level 3-4 projects)
@@ -69,7 +69,7 @@ Test architecture and quality assurance components. The **[Test Architect (TEA)
 ```bash
 # Load the PM agent - either via slash command or drag and drop or @ the agent file.
 # Once loaded, the agent should greet you and offer a menu of options. You can enter:
-`*plan-project`
+`*prd`
 ```
 
 ## Key Concepts

src/modules/bmm/testarch/README.md

@@ -18,7 +18,7 @@ TEA integrates across the entire BMad development lifecycle, providing quality a
 ┌──────────────────────────────────────────────────────────┐
 │             BMM Phase 2: PLANNING                        │
 │                                                          │
-│  PM: *plan-project                                       │
+│  PM: *prd                                       │
 │       ↓                                                  │
 │  TEA: *framework ──→ *ci ──→ *test-design                │
 │       └─────────┬─────────────┘                          │
@@ -105,7 +105,7 @@ This complexity **requires specialized documentation** (this guide), **extensive
 
 1. Run the core planning workflows first:
    - Analyst `*product-brief`
-   - Product Manager `*plan-project`
+   - Product Manager `*prd`
    - Architect `*create-architecture`
 2. Confirm `bmad/bmm/config.yaml` defines `project_name`, `output_folder`, `dev_story_location`, and language settings.
 3. Ensure a test test framework setup exists; if not, use `*framework` command to create a test framework setup, prior to development.
@@ -117,8 +117,8 @@ This complexity **requires specialized documentation** (this guide), **extensive
 ### Greenfield Feature Launch (Level 2)
 
 | Phase              | Test Architect                                                            | Dev / Team                                                            | Outputs                                                                      |
-| ------------------ | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
-| Setup              | -                                                                         | Analyst `*product-brief`, PM `*plan-project`, Architect `*create-architecture` | `{output_folder}/product-brief*.md`, `PRD.md`, `epics.md`, `architecture.md` |
+| ------------------ | ------------------------------------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+| Setup              | -                                                                         | Analyst `*product-brief`, PM `*prd`, Architect `*create-architecture` | `{output_folder}/product-brief*.md`, `PRD.md`, `epics.md`, `architecture.md` |
 | Pre-Implementation | Run `*framework` (if harness missing), `*ci`, and `*test-design`          | Review risk/design/CI guidance, align backlog                         | Test scaffold, CI pipeline, risk and coverage strategy                       |
 | Story Prep         | -                                                                         | Scrum Master `*create-story`, `*story-context`                        | Story markdown + context XML                                                 |
 | Implementation     | (Optional) Trigger `*atdd` before dev to supply failing tests + checklist | Implement story guided by ATDD checklist                              | Failing acceptance tests + implementation checklist                          |
@@ -139,7 +139,7 @@ This complexity **requires specialized documentation** (this guide), **extensive
 <details>
 <summary>Worked Example – “Nova CRM” Greenfield Feature</summary>
 
-1. **Planning:** Analyst runs `*product-brief`; PM executes `*plan-project` to produce PRD and epics; Architect completes `*create-architecture` for the new module.
+1. **Planning:** Analyst runs `*product-brief`; PM executes `*prd` to produce PRD and epics; Architect completes `*create-architecture` for the new module.
 2. **Setup:** TEA checks harness via `*framework`, configures `*ci`, and runs `*test-design` to capture risk/coverage plans.
 3. **Story Prep:** Scrum Master generates the story via `*create-story`; PO validates using `*solutioning-gate-check`.
 4. **Implementation:** TEA optionally runs `*atdd`; Dev implements with guidance from failing tests and the plan.
@@ -174,7 +174,7 @@ This complexity **requires specialized documentation** (this guide), **extensive
 <details>
 <summary>Worked Example – “Atlas Payments” Brownfield Story</summary>
 
-1. **Context Refresh:** Analyst reruns `*product-brief`; PM executes `*plan-project` to update PRD, analysis, and `epics.md`; Architect triggers `*create-architecture` capturing legacy payment flows.
+1. **Context Refresh:** Analyst reruns `*product-brief`; PM executes `*prd` to update PRD, analysis, and `epics.md`; Architect triggers `*create-architecture` capturing legacy payment flows.
 2. **Baseline Coverage:** TEA executes `*trace` to record current coverage in `docs/qa/assessments/atlas-payment-trace.md`.
 3. **Risk and Design:** `*test-design` flags settlement edge cases, plans mitigations, and allocates new API/E2E scenarios with P0 priorities.
 4. **Story Prep:** Scrum Master generates `stories/story-1.1.md` via `*create-story`, automatically pulling updated context.

src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md

@@ -89,21 +89,19 @@
 **Status Updated:**
 
 - Progress tracking updated
-  {{else}}
-  Note: Running in standalone mode (no status file).
-  To track progress across workflows, run `workflow-init` first.
-  {{/if}}
 
 **Next Steps:**
 
-1. Review game brainstorming results
-2. Consider running:
-   - `research` workflow for market/game research
-   - `game-brief` workflow to formalize game vision
-   - Or proceed directly to `plan-project` if ready
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** You can run other analysis workflows (research, game-brief) before proceeding
 
-{{#if standalone_mode != true}}
 Check status anytime with: `workflow-status`
+{{else}}
+**Next Steps:**
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
   {{/if}}
   </output>
   </step>

src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md

@@ -72,17 +72,17 @@
 {{#if standalone_mode != true}}
 **Status Updated:**
 - Progress tracking updated
-{{/if}}
 
 **Next Steps:**
-1. Review brainstorming results
-2. Consider running:
-   - `research` workflow for market/technical research
-   - `product-brief` workflow to formalize product vision
-   - Or proceed directly to `plan-project` if ready
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** You can run other analysis workflows (research, product-brief) before proceeding
 
-{{#if standalone_mode != true}}
 Check status anytime with: `workflow-status`
+{{else}}
+**Next Steps:**
+Since no workflow is in progress:
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
 {{/if}}
     </output>
   </step>

src/modules/bmm/workflows/1-analysis/document-project/instructions.md

@@ -43,7 +43,7 @@
 
   <check if="warning != ''">
     <output>{{warning}}</output>
-    <output>Note: This may be auto-invoked by plan-project for brownfield documentation.</output>
+    <output>Note: This may be auto-invoked by prd for brownfield documentation.</output>
     <ask>Continue with documentation? (y/n)</ask>
     <check if="n">
       <output>{{suggestion}}</output>
@@ -186,7 +186,7 @@ Your choice [1/2/3]:
   </invoke-workflow>
 
   <check if="success == true">
-    <output>Status updated! Next: {{next_workflow}}</output>
+    <output>Status updated!</output>
   </check>
 </check>
 
@@ -202,11 +202,19 @@ Your choice [1/2/3]:
 **Status Updated:**
 
 - Progress tracking updated
-  {{else}}
-  **Note:** Running in standalone mode
-  {{/if}}
+
+**Next Steps:**
+
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
 
 Check status anytime with: `workflow-status`
+{{else}}
+**Next Steps:**
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
   </output>
 
 </step>

src/modules/bmm/workflows/1-analysis/game-brief/instructions.md

@@ -339,13 +339,17 @@ This brief will serve as the primary input for creating the Game Design Document
 
 **Next Steps:**
 
-1. Review the game brief document
-2. Consider creating a prototype of core mechanic
-3. Run `plan-project` workflow to create GDD from this brief
-4. Validate assumptions with target players
-
 {{#if standalone_mode != true}}
+
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Consider creating a prototype of core mechanic or validating assumptions with target players before proceeding
+
 Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
   {{/if}}
   </output>
   </step>

src/modules/bmm/workflows/1-analysis/product-brief/instructions.md

@@ -303,12 +303,17 @@ This brief will serve as the primary input for creating the Product Requirements
 
 **Next Steps:**
 
-1. Review the product brief document
-2. Gather any additional stakeholder input
-3. Run `plan-project` workflow to create PRD from this brief
-
 {{#if standalone_mode != true}}
+
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Gather additional stakeholder input or run research workflows before proceeding
+
 Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
   {{/if}}
   </output>
   </step>

src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md

@@ -403,9 +403,8 @@ Select option (1-4):</ask>
 
 **Next Steps:**
 
-1. Execute the research prompt with your chosen AI platform
-2. Gather and analyze findings
-3. Run `plan-project` to incorporate findings
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Execute the research prompt with AI platform, gather findings, or run additional research workflows
 
 Check status anytime with: `workflow-status`
 </output>
@@ -422,8 +421,11 @@ Note: Running in standalone mode (no status file).
 
 **Next Steps:**
 
-1. Execute the research prompt with AI platform
-2. Run plan-project workflow
+Since no workflow is in progress:
+
+- Execute the research prompt with AI platform and gather findings
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
   </output>
   </check>
   </step>

src/modules/bmm/workflows/1-analysis/research/instructions-market.md

@@ -583,11 +583,8 @@ Create compelling executive summary with:
 
 **Next Steps:**
 
-1. Review research findings
-2. Share with stakeholders
-3. Consider running:
-   - `product-brief` or `game-brief` to formalize vision
-   - `plan-project` if ready to create PRD/GDD
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief, game-brief, etc.)
 
 Check status anytime with: `workflow-status`
 </output>
@@ -602,12 +599,13 @@ Check status anytime with: `workflow-status`
 
 Note: Running in standalone mode (no status file).
 
-To track progress across workflows, run `workflow-status` first.
-
 **Next Steps:**
 
-1. Review research findings
-2. Run product-brief or plan-project workflows
+Since no workflow is in progress:
+
+- Review research findings
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
   </output>
   </check>
   </step>

src/modules/bmm/workflows/1-analysis/research/instructions-technical.md

@@ -471,9 +471,8 @@ Select option (1-5):</ask>
 
 **Next Steps:**
 
-1. Review technical research findings
-2. Share with architecture team
-3. Run `plan-project` to incorporate findings into PRD
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Review findings with architecture team, or run additional analysis workflows
 
 Check status anytime with: `workflow-status`
 </output>
@@ -490,8 +489,11 @@ Note: Running in standalone mode (no status file).
 
 **Next Steps:**
 
-1. Review technical research findings
-2. Run plan-project workflow
+Since no workflow is in progress:
+
+- Review technical research findings
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
   </output>
   </check>
   </step>

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md

@@ -1256,33 +1256,27 @@ Open in browser to explore!</output>
 
 **Recommended Next Steps:**
 
-1. **Validate UX Specification** (Recommended first!) - Run the validation checklist with \*validate-design
-   - Ensures collaborative process was followed
-   - Validates visual artifacts were generated
-   - Confirms decision rationale is documented
-   - Verifies implementation readiness
+{{#if tracking_mode == true}}
 
-2. **Follow-Up Workflows** - This specification can serve as input to:
-   - **Wireframe Generation Workflow** - Create detailed wireframes from user flows
-   - **Figma Design Workflow** - Generate Figma files via MCP integration
-   - **Interactive Prototype Workflow** - Build clickable HTML prototypes
-   - **Component Showcase Workflow** - Create interactive component library
-   - **AI Frontend Prompt Workflow** - Generate prompts for v0, Lovable, Bolt
-   - **Solution Architecture Workflow** - Define technical architecture with UX context
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Run validation with \*validate-design, or generate additional UX artifacts (wireframes, prototypes, etc.)
 
-As additional workflows are run, they will add their outputs to the "Optional Enhancement Deliverables" section of the UX specification.
+Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Run validation checklist with \*validate-design (recommended)
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+
+**Optional Follow-Up Workflows:**
+
+- Wireframe Generation / Figma Design / Interactive Prototype workflows
+- Component Showcase / AI Frontend Prompt workflows
+- Solution Architecture workflow (with UX context)
+  {{/if}}
   </output>
 
-  <check if="tracking_mode == true">
-    <output>
-
-**Planning Workflow Integration:**
-
-Status updated. Next suggested workflow: {{next_workflow_from_status}}
-Run with: workflow {{next_workflow_name}}
-</output>
-</check>
-
 <template-output>completion_summary</template-output>
 </step>
 

src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md

@@ -428,19 +428,10 @@ For each epic from the epic list, expand with full story details:
 
 **Next Steps:**
 
-{{#if project_level == 2}}
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Review PRD and epics with stakeholders, or run `create-design` if you have UI requirements
 
-- Review PRD and epics with stakeholders
-- **Next:** Run `tech-spec` for lightweight technical planning
-- Then proceed to implementation
-  {{/if}}
-
-{{#if project_level >= 3}}
-
-- Review PRD and epics with stakeholders
-- **Next:** Run `create-architecture` for full technical design
-- Then proceed to implementation
-  {{/if}}
+Check status anytime with: `workflow-status`
 
 Would you like to:
 

src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md

@@ -226,47 +226,40 @@ Run cohesion validation? (y/n)</ask>
 - **Ready for sprint planning with epic/story breakdown**
 </check>
 
-## Next Steps Checklist
+## Next Steps
 
-<action>Determine appropriate next steps for Level 0 atomic change</action>
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+  <param>mode: update</param>
+  <param>action: complete_workflow</param>
+  <param>workflow_name: tech-spec</param>
+</invoke-workflow>
 
-**Optional Next Steps:**
-
-<check if="change involves UI components">
-  - [ ] **Create simple UX documentation** (if UI change is user-facing)
-    - Note: Full instructions-ux workflow may be overkill for Level 0
-    - Consider documenting just the specific UI change
+<check if="success == true">
+  <output>Status updated!</output>
 </check>
 
-- [ ] **Generate implementation task**
-  - Command: `workflow task-generation`
-  - Uses: tech-spec.md
+<output>**✅ Tech-Spec Complete, {user_name}!**
 
-<check if="change is backend/API only">
-
-**Recommended Next Steps:**
-
-- [ ] **Create test plan** for the change
-  - Unit tests for the specific change
-  - Integration test if affects other components
-
-- [ ] **Generate implementation task**
-  - Command: `workflow task-generation`
-  - Uses: tech-spec.md
-
-<ask>**✅ Tech-Spec Complete, {user_name}!**
-
-Next action:
-
-1. Proceed to implementation
-2. Generate development task
-3. Create test plan
-4. Exit workflow
-
-Select option (1-4):</ask>
+**Deliverables Created:**
+<check if="project_level == 0">
 
+- ✅ tech-spec.md - Technical specification
+- ✅ user-story.md - Single user story
   </check>
 
+<check if="project_level == 1">
+- ✅ tech-spec.md - Technical specification
+- ✅ epics.md - Epic and story breakdown
+</check>
+
+**Next Steps:**
+
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Create test plan or document UI changes if applicable
+
+Check status anytime with: `workflow-status`
+</output>
+
 </step>
 
 </workflow>

src/modules/bmm/workflows/3-solutioning/architecture/instructions.md

@@ -668,9 +668,7 @@ Enforcement: "All agents MUST follow this pattern"
   <check if="success == true">
     <output>✅ Decision Architecture workflow complete!
 
-    Status updated. Next steps:
-    - Review the architecture.md document
-    - {{next_workflow_suggestion}} ({{next_agent}} agent)
+Status updated.
 </output>
 
   </check>
@@ -686,6 +684,13 @@ Enforcement: "All agents MUST follow this pattern"
   {{/if_starter_template}}
 
 The architecture is ready to guide AI agents through consistent implementation.
+
+**Next Steps:**
+
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- Review the architecture.md document before proceeding
+
+Check status anytime with: `workflow-status`
 </output>
 
 <template-output>completion_summary</template-output>

src/modules/bmm/workflows/README.md

@@ -32,7 +32,7 @@ The BMM (BMAD Method Module) orchestrates software development through four dist
 │                    PHASE 2: PLANNING                         │
 │              (Scale-Adaptive Router - by type)               │
 ├──────────────────────────────────────────────────────────────┤
-│  SOFTWARE: plan-project          GAMES: gdd            │
+│  SOFTWARE: prd          GAMES: gdd            │
 │      ├──→ Level 0: tech-spec only      ├──→ GDD (all levels) │
 │      ├──→ Level 1: tech-spec only      └──→ Narrative design │
 │      ├──→ Level 2: PRD + tech-spec                           │
@@ -358,7 +358,7 @@ Status: Done        (User approved via story-done, DoD complete)
 ### Brownfield Projects
 
 ```
-plan-project (Phase 2)
+workflow-init (Phase 2)
     ├─→ Check: Is existing codebase documented?
     │   ├─→ YES: Proceed with planning
     │   └─→ NO: HALT with message:
@@ -454,7 +454,7 @@ plan-project (Phase 2)
 | Creating all tech specs upfront   | Use JIT approach - one epic at a time |
 | Skipping story-context generation | Always run after create-story         |
 | Batching story creation           | Create one story at a time            |
-| Ignoring scale levels             | Let plan-project determine level      |
+| Ignoring scale levels             | Let workflow init determine level     |
 | Planning brownfield without docs  | Run brownfield-analysis first         |
 | Not running retrospectives        | Schedule after every epic             |
 

src/modules/bmm/workflows/testarch/framework/README.md

@@ -130,7 +130,7 @@ Automatically consults TEA knowledge base:
 
 **Before framework:**
 
-- **plan-project** (Phase 2): Determines project scope and testing needs
+- **prd** (Phase 2): Determines project scope and testing needs
 - **workflow-status**: Verifies project readiness
 
 **After framework:**

src/modules/bmm/workflows/testarch/test-design/README.md

@@ -304,7 +304,7 @@ Automatically consults TEA knowledge base:
 
 **Before test-design:**
 
-- **plan-project** (Phase 2): Creates PRD and epics
+- **prd** (Phase 2): Creates PRD and epics
 - **architecture** (Phase 3): Defines technical approach
 - **tech-spec** (Phase 3): Implementation details
 

src/modules/bmm/workflows/workflow-status/paths/brownfield-level-2.yaml

@@ -44,6 +44,10 @@ phases:
         command: "prd"
         output: "Focused PRD for new features"
         note: "Must consider existing system constraints"
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
       - id: "tech-spec"
         required: true
         agent: "pm"

src/modules/bmm/workflows/workflow-status/paths/brownfield-level-3.yaml

@@ -44,6 +44,10 @@ phases:
         agent: "pm"
         command: "prd"
         output: "Requirements with integration points"
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
       - id: "create-design"
         conditional: "if_has_ui"
         agent: "ux-designer"
@@ -69,6 +73,10 @@ phases:
         agent: "architect"
         command: "create-architecture"
         note: "Extension of existing architecture"
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"

src/modules/bmm/workflows/workflow-status/paths/brownfield-level-4.yaml

@@ -46,6 +46,10 @@ phases:
         agent: "pm"
         command: "prd"
         output: "Comprehensive PRD considering existing system"
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
       - id: "create-design"
         required: true
         agent: "ux-designer"
@@ -62,6 +66,10 @@ phases:
         command: "create-architecture"
         output: "Architecture for system expansion"
         note: "Must maintain backward compatibility"
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"

src/modules/bmm/workflows/workflow-status/paths/game-design.yaml

@@ -50,6 +50,10 @@ phases:
         agent: "architect"
         command: "create-architecture"
         note: "Engine architecture, networking, systems"
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"

src/modules/bmm/workflows/workflow-status/paths/greenfield-level-2.yaml

@@ -34,6 +34,10 @@ phases:
         agent: "pm"
         command: "prd"
         output: "Creates PRD with epics.md and story list"
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
       - id: "create-design"
         conditional: "if_has_ui"
         agent: "ux-designer"
@@ -53,6 +57,10 @@ phases:
         agent: "architect"
         command: "create-architecture"
         output: "System-wide architecture document"
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"

src/modules/bmm/workflows/workflow-status/paths/greenfield-level-3.yaml

@@ -34,6 +34,10 @@ phases:
         agent: "pm"
         command: "prd"
         output: "High-level requirements and epic definitions"
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
       - id: "create-design"
         conditional: "if_has_ui"
         agent: "ux-designer"
@@ -48,6 +52,10 @@ phases:
         agent: "architect"
         command: "create-architecture"
         output: "System-wide architecture document"
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"

src/modules/bmm/workflows/workflow-status/paths/greenfield-level-4.yaml

@@ -35,6 +35,10 @@ phases:
         agent: "pm"
         command: "prd"
         output: "Comprehensive product requirements document"
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
       - id: "create-design"
         required: true
         agent: "ux-designer"
@@ -50,6 +54,10 @@ phases:
         agent: "architect"
         command: "create-architecture"
         output: "Enterprise architecture documentation"
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"