@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.3

package/src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md

@@ -1,63 +1,63 @@
----
-name: validate-prd
-description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
-main_config: '{project-root}/_bmad/bmm/config.yaml'
-validateWorkflow: './steps-v/step-v-01-discovery.md'
----
-
-# PRD Validate Workflow
-
-**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
-
-**Your Role:** Validation Architect and Quality Assurance Specialist.
-
-You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, read fully and follow the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from {main_config} and resolve:
-
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as system-generated current datetime
-
-✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
-
-### 2. Route to Validate Workflow
-
-"**Validate Mode: Validating an existing PRD against BMAD standards.**"
-
-Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
+---
+name: validate-prd
+description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
+main_config: '{project-root}/_bmad/bmm/config.yaml'
+validateWorkflow: './steps-v/step-v-01-discovery.md'
+---
+
+# PRD Validate Workflow
+
+**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
+
+**Your Role:** Validation Architect and Quality Assurance Specialist.
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+
+### 2. Route to Validate Workflow
+
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+
+Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md

@@ -1,63 +1,63 @@
-# Step 1B: UX Design Workflow Continuation
-
-Resume the UX design workflow from where it was left off.
-
-## CONTINUATION SEQUENCE
-
-### 1. Analyze Current State
-
-Review the frontmatter to understand:
-- `stepsCompleted`: Which steps are already done
-- `lastStep`: The most recently completed step number
-- `inputDocuments`: What context was already loaded
-- All other frontmatter variables
-
-### 2. Load All Input Documents
-
-Reload each document listed in `inputDocuments` completely. Do not discover new documents — only reload what was previously processed.
-
-### 3. Summarize Current Progress
-
-"Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
-
-**Current Progress:**
-- Steps completed: {stepsCompleted}
-- Last worked on: Step {lastStep}
-- Context documents available: {len(inputDocuments)} files
-
-**Document Status:**
-- Current UX design document is ready with all completed sections
-
-Does this look right, or do you want to make any adjustments before we proceed?"
-
-### 4. Determine Next Step
-
-Based on `lastStep` value, determine which step to load next:
-- If `lastStep = 1` → Load step-02-discovery.md
-- If `lastStep = 2` → Load step-03-core-experience.md
-- If `lastStep = 3` → Load step-04-emotional-response.md
-- Continue this pattern for all steps
-- If `lastStep` indicates final step → Workflow already complete (see below)
-
-### 5. Present Continuation Options
-
-"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
-
-[AR] Adversarial Review [C] Continue to Step {nextStepNumber}"
-
-After user selects [C], load the appropriate next step file.
-
-## WORKFLOW ALREADY COMPLETE?
-
-If `lastStep` indicates the final step is completed:
-
-"Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
-
-The final UX design specification is ready at `{output_folder}/ux-design-specification.md` with all sections completed through step {finalStepNumber}.
-
-Would you like me to:
-- Review the completed UX design specification with you
-- Suggest next workflow steps (like wireframe generation or architecture)
-- Start a new UX design revision
-
-What would be most helpful?"
+# Step 1B: UX Design Workflow Continuation
+
+Resume the UX design workflow from where it was left off.
+
+## CONTINUATION SEQUENCE
+
+### 1. Analyze Current State
+
+Review the frontmatter to understand:
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `inputDocuments`: What context was already loaded
+- All other frontmatter variables
+
+### 2. Load All Input Documents
+
+Reload each document listed in `inputDocuments` completely. Do not discover new documents — only reload what was previously processed.
+
+### 3. Summarize Current Progress
+
+"Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
+
+**Current Progress:**
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+- Current UX design document is ready with all completed sections
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 4. Determine Next Step
+
+Based on `lastStep` value, determine which step to load next:
+- If `lastStep = 1` → Load step-02-discovery.md
+- If `lastStep = 2` → Load step-03-core-experience.md
+- If `lastStep = 3` → Load step-04-emotional-response.md
+- Continue this pattern for all steps
+- If `lastStep` indicates final step → Workflow already complete (see below)
+
+### 5. Present Continuation Options
+
+"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+
+[AR] Adversarial Review [C] Continue to Step {nextStepNumber}"
+
+After user selects [C], load the appropriate next step file.
+
+## WORKFLOW ALREADY COMPLETE?
+
+If `lastStep` indicates the final step is completed:
+
+"Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
+
+The final UX design specification is ready at `{output_folder}/ux-design-specification.md` with all sections completed through step {finalStepNumber}.
+
+Would you like me to:
+- Review the completed UX design specification with you
+- Suggest next workflow steps (like wireframe generation or architecture)
+- Start a new UX design revision
+
+What would be most helpful?"

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md

@@ -1,106 +1,106 @@
-# Step 2: Project Understanding
-
-Understand the project context, target users, and what makes this product special from a UX perspective.
-
-## PROJECT DISCOVERY SEQUENCE
-
-### 1. Review Loaded Context
-
-Analyze what we know from the loaded documents:
-
-"Based on the project documentation we have loaded, let me confirm what I'm understanding about {{project_name}}.
-
-**From the documents:**
-{summary of key insights from loaded PRD, briefs, and other context documents}
-
-**Target Users:**
-{summary of user information from loaded documents}
-
-**Key Features/Goals:**
-{summary of main features and goals from loaded documents}
-
-Does this match your understanding? Are there any corrections or additions you'd like to make?"
-
-### 2. Fill Context Gaps (If no documents or gaps exist)
-
-If no documents were loaded or key information is missing:
-
-"Since we don't have complete documentation, let's start with the essentials:
-
-**What are you building?** (Describe your product in 1-2 sentences)
-
-**Who is this for?** (Describe your ideal user or target audience)
-
-**What makes this special or different?** (What's the unique value proposition?)
-
-**What's the main thing users will do with this?** (Core user action or goal)"
-
-### 3. Explore User Context
-
-"Let me understand your users better to inform the UX design:
-
-- What problem are users trying to solve?
-- What frustrates them with current solutions?
-- What would make them say 'this is exactly what I needed'?
-- How tech-savvy are your target users?
-- What devices will they use most?
-- When/where will they use this product?"
-
-### 4. Identify UX Design Challenges
-
-"From what we've discussed, I'm seeing some key UX design considerations:
-
-**Design Challenges:**
-- [Identify 2-3 key UX challenges based on project type and user needs]
-- [Note any platform-specific considerations]
-- [Highlight any complex user flows or interactions]
-
-**Design Opportunities:**
-- [Identify 2-3 areas where great UX could create competitive advantage]
-- [Note any opportunities for innovative UX patterns]
-
-Does this capture the key UX considerations we need to address?"
-
-### 5. Generate Project Understanding Content
-
-When saving to document, append these sections:
-
-```markdown
-## Executive Summary
-
-### Project Vision
-
-[Project vision summary based on conversation]
-
-### Target Users
-
-[Target user descriptions based on conversation]
-
-### Key Design Challenges
-
-[Key UX challenges identified based on conversation]
-
-### Design Opportunities
-
-[Design opportunities identified based on conversation]
-```
-
-### 6. Present Content and Menu
-
-"I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 5]
-
-**What would you like to do?**
-[AR] Adversarial Review [C] Continue - Save this to the document and move to core experience definition"
-
-### 7. Handle Menu Selection
-
-**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — pass the current content as the content to review; display findings with recommendations; then redisplay this menu.
-
-**If C:**
-- Append the final content to `{planning_artifacts}/ux-design-specification.md`
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md`
+# Step 2: Project Understanding
+
+Understand the project context, target users, and what makes this product special from a UX perspective.
+
+## PROJECT DISCOVERY SEQUENCE
+
+### 1. Review Loaded Context
+
+Analyze what we know from the loaded documents:
+
+"Based on the project documentation we have loaded, let me confirm what I'm understanding about {{project_name}}.
+
+**From the documents:**
+{summary of key insights from loaded PRD, briefs, and other context documents}
+
+**Target Users:**
+{summary of user information from loaded documents}
+
+**Key Features/Goals:**
+{summary of main features and goals from loaded documents}
+
+Does this match your understanding? Are there any corrections or additions you'd like to make?"
+
+### 2. Fill Context Gaps (If no documents or gaps exist)
+
+If no documents were loaded or key information is missing:
+
+"Since we don't have complete documentation, let's start with the essentials:
+
+**What are you building?** (Describe your product in 1-2 sentences)
+
+**Who is this for?** (Describe your ideal user or target audience)
+
+**What makes this special or different?** (What's the unique value proposition?)
+
+**What's the main thing users will do with this?** (Core user action or goal)"
+
+### 3. Explore User Context
+
+"Let me understand your users better to inform the UX design:
+
+- What problem are users trying to solve?
+- What frustrates them with current solutions?
+- What would make them say 'this is exactly what I needed'?
+- How tech-savvy are your target users?
+- What devices will they use most?
+- When/where will they use this product?"
+
+### 4. Identify UX Design Challenges
+
+"From what we've discussed, I'm seeing some key UX design considerations:
+
+**Design Challenges:**
+- [Identify 2-3 key UX challenges based on project type and user needs]
+- [Note any platform-specific considerations]
+- [Highlight any complex user flows or interactions]
+
+**Design Opportunities:**
+- [Identify 2-3 areas where great UX could create competitive advantage]
+- [Note any opportunities for innovative UX patterns]
+
+Does this capture the key UX considerations we need to address?"
+
+### 5. Generate Project Understanding Content
+
+When saving to document, append these sections:
+
+```markdown
+## Executive Summary
+
+### Project Vision
+
+[Project vision summary based on conversation]
+
+### Target Users
+
+[Target user descriptions based on conversation]
+
+### Key Design Challenges
+
+[Key UX challenges identified based on conversation]
+
+### Design Opportunities
+
+[Design opportunities identified based on conversation]
+```
+
+### 6. Present Content and Menu
+
+"I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 5]
+
+**What would you like to do?**
+[AR] Adversarial Review [C] Continue - Save this to the document and move to core experience definition"
+
+### 7. Handle Menu Selection
+
+**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — pass the current content as the content to review; display findings with recommendations; then redisplay this menu.
+
+**If C:**
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md`