@devo-bmad-custom/agent-orchestration 1.0.0

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

@@ -0,0 +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)

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

@@ -0,0 +1,63 @@
+## Step 0: Load writing-skills
+
+Invoke `writing-skills` now. Do not proceed to Step 1 until writing-skills is loaded.
+
+---
+
+# Step 1: UX Design Workflow Initialization
+
+Initialize the UX design workflow by detecting continuation state and setting up the design specification document.
+
+## INITIALIZATION SEQUENCE
+
+### 1. Check for Existing Workflow
+
+Check if the output document already exists at `{planning_artifacts}/*ux-design-specification*.md`.
+
+- If it exists and has frontmatter with `stepsCompleted`: **STOP** and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md` immediately.
+- If no document exists, proceed with fresh workflow setup below.
+
+### 2. Fresh Workflow Setup
+
+#### A. Input Document Discovery
+
+Discover and load context documents from these locations: `{planning_artifacts}/**`, `{output_folder}/**`, `{product_knowledge}/**`, `docs/**`.
+
+Documents can be a single markdown file or a folder with an index and multiple files. If searching for `*foo*.md` and not found, also search for a folder called `*foo*/index.md`.
+
+Try to discover:
+- Product Brief (`*brief*.md`)
+- Research Documents (`*prd*.md`)
+- Project Documentation (generally multiple documents in `{product_knowledge}` or `docs`)
+- Project Context (`**/project-context.md`)
+
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules.</critical>
+
+**Loading Rules:**
+- Load ALL confirmed files completely (no offset/limit)
+- If there is a project context, bias the remainder of the workflow accordingly
+- For sharded folders, load ALL files using the index first to understand each document
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+Copy the template from `{installed_path}/ux-design-template.md` to `{planning_artifacts}/ux-design-specification.md` and initialize frontmatter.
+
+#### C. Report to User
+
+"Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
+
+**Documents Found:**
+- PRD: {number of PRD files loaded or "None found"}
+- Product brief: {number of brief files loaded or "None found"}
+- Other context: {number of other files loaded or "None found"}
+
+**Files loaded:** {list of specific file names or "No additional documents found"}
+
+Do you have any other documents you'd like me to include, or shall we continue to the next step?
+
+[AR] Adversarial Review [C] Continue to UX discovery"
+
+## NEXT STEP
+
+After user selects [C]: ensure `{planning_artifacts}/ux-design-specification.md` has been created and saved with `stepsCompleted: [1]` in frontmatter, then load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md`.

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

@@ -0,0 +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?"

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

@@ -0,0 +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`

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md

@@ -0,0 +1,111 @@
+# Step 3: Core Experience Definition
+
+Define the core user experience, platform requirements, and what makes the interaction effortless.
+
+## CORE EXPERIENCE DISCOVERY SEQUENCE
+
+### 1. Define Core User Action
+
+"Now let's dig into the heart of the user experience for {{project_name}}.
+
+**Core Experience Questions:**
+- What's the ONE thing users will do most frequently?
+- What user action is absolutely critical to get right?
+- What should be completely effortless for users?
+- If we nail one interaction, everything else follows — what is it?
+
+Think about the core loop or primary action that defines your product's value."
+
+### 2. Explore Platform Requirements
+
+"Let's define the platform context for {{project_name}}:
+
+- Web, mobile app, desktop, or multiple platforms?
+- Will this be primarily touch-based or mouse/keyboard?
+- Any specific platform requirements or constraints?
+- Do we need to consider offline functionality?
+- Any device-specific capabilities we should leverage?"
+
+### 3. Identify Effortless Interactions
+
+"**Effortless Experience Design:**
+- What user actions should feel completely natural and require zero thought?
+- Where do users currently struggle with similar products?
+- What interaction, if made effortless, would create delight?
+- What should happen automatically without user intervention?
+- Where can we eliminate steps that competitors require?"
+
+### 4. Define Critical Success Moments
+
+"**Critical Success Moments:**
+- What's the moment where users realize 'this is better'?
+- When does the user feel successful or accomplished?
+- What interaction, if failed, would ruin the experience?
+- What are the make-or-break user flows?
+- Where does first-time user success happen?"
+
+### 5. Synthesize Experience Principles
+
+"Based on our discussion, I'm hearing these core experience principles for {{project_name}}:
+
+**Experience Principles:**
+- [Principle 1 based on core action focus]
+- [Principle 2 based on effortless interactions]
+- [Principle 3 based on platform considerations]
+- [Principle 4 based on critical success moments]
+
+These principles will guide all our UX decisions. Do these capture what's most important?"
+
+### 6. Generate Core Experience Content
+
+When saving to document, append these sections:
+
+```markdown
+## Core User Experience
+
+### Defining Experience
+
+[Core experience definition based on conversation]
+
+### Platform Strategy
+
+[Platform requirements and decisions based on conversation]
+
+### Effortless Interactions
+
+[Effortless interaction areas identified based on conversation]
+
+### Critical Success Moments
+
+[Critical success moments defined based on conversation]
+
+### Experience Principles
+
+[Guiding principles for UX decisions based on conversation]
+```
+
+### 7. Present Content and Menu
+
+"I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 6]
+
+**What would you like to do?**
+[A] Advanced Elicitation - Let's refine the core experience definition
+[P] Party Mode - Bring different perspectives on the user experience
+[AR] Adversarial Review [C] Continue - Save this to the document and move to emotional response definition"
+
+### 8. Handle Menu Selection
+
+**If A:** Read fully and follow `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` with the current content. Ask user to accept/reject improvements, then return to menu.
+
+**If P:** Read fully and follow `{project-root}/_bmad/core/workflows/party-mode/workflow.md` with the current content. Ask user to accept/reject changes, then return to menu.
+
+**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings with recommendations; then redisplay this menu.
+
+**If C:**
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
+- Update frontmatter: append step to end of stepsCompleted array
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md`

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md

@@ -0,0 +1,115 @@
+# Step 4: Desired Emotional Response
+
+Define the desired emotional responses users should feel when using the product.
+
+## EMOTIONAL RESPONSE DISCOVERY SEQUENCE
+
+### 1. Explore Core Emotional Goals
+
+"Now let's think about how {{project_name}} should make users feel.
+
+**Emotional Response Questions:**
+- What should users FEEL when using this product?
+- What emotion would make them tell a friend about this?
+- How should users feel after accomplishing their primary goal?
+- What feeling differentiates this from competitors?
+
+Common emotional goals: Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged?"
+
+### 2. Identify Emotional Journey Mapping
+
+"**Emotional Journey Considerations:**
+- How should users feel when they first discover the product?
+- What emotion during the core experience/action?
+- How should they feel after completing their task?
+- What if something goes wrong — what emotional response do we want?
+- How should they feel when returning to use it again?"
+
+### 3. Define Micro-Emotions
+
+"**Micro-Emotions to Consider:**
+- Confidence vs. Confusion
+- Trust vs. Skepticism
+- Excitement vs. Anxiety
+- Accomplishment vs. Frustration
+- Delight vs. Satisfaction
+- Belonging vs. Isolation
+
+Which of these emotional states are most critical for your product's success?"
+
+### 4. Connect Emotions to UX Decisions
+
+"**Design Implications:**
+- If we want users to feel [emotional state], what UX choices support this?
+- What interactions might create negative emotions we want to avoid?
+- Where can we add moments of delight or surprise?
+- How do we build trust and confidence through design?
+
+**Emotion-Design Connections:**
+- [Emotion 1] → [UX design approach]
+- [Emotion 2] → [UX design approach]
+- [Emotion 3] → [UX design approach]"
+
+### 5. Validate Emotional Goals
+
+"Let me make sure I understand the emotional vision for {{project_name}}:
+
+**Primary Emotional Goal:** [Summarize main emotional response]
+**Secondary Feelings:** [List supporting emotional states]
+**Emotions to Avoid:** [List negative emotions to prevent]
+
+Does this capture the emotional experience you want to create? Any adjustments needed?"
+
+### 6. Generate Emotional Response Content
+
+When saving to document, append these sections:
+
+```markdown
+## Desired Emotional Response
+
+### Primary Emotional Goals
+
+[Primary emotional goals based on conversation]
+
+### Emotional Journey Mapping
+
+[Emotional journey mapping based on conversation]
+
+### Micro-Emotions
+
+[Micro-emotions identified based on conversation]
+
+### Design Implications
+
+[UX design implications for emotional responses based on conversation]
+
+### Emotional Design Principles
+
+[Guiding principles for emotional design based on conversation]
+```
+
+### 7. Present Content and Menu
+
+"I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 6]
+
+**What would you like to do?**
+[A] Advanced Elicitation - Let's refine the emotional response definition
+[P] Party Mode - Bring different perspectives on user emotional needs
+[AR] Adversarial Review [C] Continue - Save this to the document and move to inspiration analysis"
+
+### 8. Handle Menu Selection
+
+**If A:** Read fully and follow `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` with the current content. Ask user to accept/reject improvements, then return to menu.
+
+**If P:** Read fully and follow `{project-root}/_bmad/core/workflows/party-mode/workflow.md` with the current content. Ask user to accept/reject changes, then return to menu.
+
+**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings with recommendations; then redisplay this menu.
+
+**If C:**
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
+- Update frontmatter: append step to end of stepsCompleted array
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md`

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md

@@ -0,0 +1,127 @@
+# Step 5: UX Pattern Analysis & Inspiration
+
+Analyze inspiring products and UX patterns to inform design decisions for the current project.
+
+## INSPIRATION ANALYSIS SEQUENCE
+
+### 1. Identify User's Favorite Apps
+
+"Let's learn from products your users already love and use regularly.
+
+**Inspiration Questions:**
+- Name 2-3 apps your target users already love and USE frequently
+- For each one, what do they do well from a UX perspective?
+- What makes the experience compelling or delightful?
+- What keeps users coming back to these apps?
+
+Think about apps in your category or even unrelated products that have great UX."
+
+### 2. Analyze UX Patterns and Principles
+
+For each inspiring app:
+
+"**For [App Name]:**
+- What core problem does it solve elegantly?
+- What makes the onboarding experience effective?
+- How do they handle navigation and information hierarchy?
+- What are their most innovative or delightful interactions?
+- What visual design choices support the user experience?
+- How do they handle errors or edge cases?"
+
+### 3. Extract Transferable Patterns
+
+"**Transferable UX Patterns:**
+Looking across these inspiring apps, I see patterns we could adapt:
+
+**Navigation Patterns:**
+- [Pattern 1] - could work for your [specific use case]
+- [Pattern 2] - might solve your [specific challenge]
+
+**Interaction Patterns:**
+- [Pattern 1] - excellent for [your user goal]
+- [Pattern 2] - addresses [your user pain point]
+
+**Visual Patterns:**
+- [Pattern 1] - supports your [emotional goal]
+- [Pattern 2] - aligns with your [platform requirements]
+
+Which of these patterns resonate most for your product?"
+
+### 4. Identify Anti-Patterns to Avoid
+
+"**UX Anti-Patterns to Avoid:**
+From analyzing both successes and failures in your space, here are patterns to avoid:
+
+- [Anti-pattern 1] - users find this confusing/frustrating
+- [Anti-pattern 2] - this creates unnecessary friction
+- [Anti-pattern 3] - doesn't align with your [emotional goals]
+
+Learning from others' mistakes is as important as learning from their successes."
+
+### 5. Define Design Inspiration Strategy
+
+"**Design Inspiration Strategy:**
+
+**What to Adopt:**
+- [Specific pattern] - because it supports [your core experience]
+- [Specific pattern] - because it aligns with [user needs]
+
+**What to Adapt:**
+- [Specific pattern] - modify for [your unique requirements]
+- [Specific pattern] - simplify for [your user skill level]
+
+**What to Avoid:**
+- [Specific anti-pattern] - conflicts with [your goals]
+- [Specific anti-pattern] - doesn't fit [your platform]
+
+This strategy will guide our design decisions while keeping {{project_name}} unique."
+
+### 6. Generate Inspiration Analysis Content
+
+When saving to document, append these sections:
+
+```markdown
+## UX Pattern Analysis & Inspiration
+
+### Inspiring Products Analysis
+
+[Analysis of inspiring products based on conversation]
+
+### Transferable UX Patterns
+
+[Transferable patterns identified based on conversation]
+
+### Anti-Patterns to Avoid
+
+[Anti-patterns to avoid based on conversation]
+
+### Design Inspiration Strategy
+
+[Strategy for using inspiration based on conversation]
+```
+
+### 7. Present Content and Menu
+
+"I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 6]
+
+**What would you like to do?**
+[A] Advanced Elicitation - Let's deepen our UX pattern analysis
+[P] Party Mode - Bring different perspectives on inspiration sources
+[AR] Adversarial Review [C] Continue - Save this to the document and move to design system choice"
+
+### 8. Handle Menu Selection
+
+**If A:** Read fully and follow `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` with the current content. Ask user to accept/reject improvements, then return to menu.
+
+**If P:** Read fully and follow `{project-root}/_bmad/core/workflows/party-mode/workflow.md` with the current content. Ask user to accept/reject changes, then return to menu.
+
+**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings with recommendations; then redisplay this menu.
+
+**If C:**
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
+- Update frontmatter: append step to end of stepsCompleted array
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md`