ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

refactor: complete display tag migration across all workflows 

Convert remaining bare quote output blocks and Display: patterns
to <display> tags in 48 files across product-brief, ux-design,
architecture, check-implementation-readiness, quick-spec, research,
brainstorming, party-mode, generate-project-context, and
document-project workflows. Fix orphaned quote artifact in
step-09-functional.md.
This commit is contained in:
Alex Verkhovsky 2026-02-01 14:04:43 -07:00
parent 7746b8f066
commit 35c7ec55d1
48 changed files with 610 additions and 313 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md
View File

@ -117,7 +117,8 @@ Try to discover the following:
#### C. Present Initialization Results
**Setup Report to User:**
"Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
<display>
Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
**Document Setup:**
@ -133,7 +134,8 @@ Try to discover the following:
**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?"
Do you have any other documents you'd like me to include, or shall we continue to the next step?
</display>
### 4. Present MENU OPTIONS

12
src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md
View File

@ -75,7 +75,8 @@ Review the frontmatter to understand:
### 3. Present Current Progress
**Progress Report to User:**
"Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
<display>
Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
**Current Progress:**
@ -88,7 +89,8 @@ Review the frontmatter to understand:
- Current product brief is ready with all completed sections
- Ready to continue from where we left off
Does this look right, or do you want to make any adjustments before we proceed?"
Does this look right, or do you want to make any adjustments before we proceed?
</display>
### 4. Determine Continuation Path
@ -104,7 +106,8 @@ Based on `lastStep` value, determine which step to load next:
### 5. Handle Workflow Completion
**If workflow already complete (`lastStep = 6`):**
"Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
<display>
Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
The final document is ready at `{outputFile}` with all sections completed through step 6.
@ -114,7 +117,8 @@ Would you like me to:
- Suggest next workflow steps (like PRD creation)
- Start a new product brief revision
What would be most helpful?"
What would be most helpful?
</display>
### 6. Present MENU OPTIONS

12
src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md
View File

@ -61,7 +61,8 @@ Conduct comprehensive product vision discovery to define the core problem, solut
### 1. Begin Vision Discovery
**Opening Conversation:**
"As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation.
<display>
As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation.
**Tell me about the product you envision:**
@ -70,7 +71,8 @@ Conduct comprehensive product vision discovery to define the core problem, solut
- What would success look like for the people you're helping?
- What excites you most about this solution?
Let's start with the problem space before we get into solutions."
Let's start with the problem space before we get into solutions.
</display>
### 2. Deep Problem Understanding
@ -147,12 +149,14 @@ Prepare the following structure for document append:
### 7. Present MENU OPTIONS
**Content Presentation:**
"I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
<display>
I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
**Here's what I'll add to the document:**
[Show the complete markdown content from step 6]
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>
#### Menu Handling Logic:

12
src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md
View File

@ -61,7 +61,8 @@ Define target users with rich personas and map their key interactions with the p
### 1. Begin User Discovery
**Opening Exploration:**
"Now that we understand what {{project_name}} does, let's define who it's for.
<display>
Now that we understand what {{project_name}} does, let's define who it's for.
**User Discovery:**
@ -70,7 +71,8 @@ Define target users with rich personas and map their key interactions with the p
- Who gets the most value from this solution?
- Are there primary users and secondary users we should consider?
Let's start by identifying the main user groups."
Let's start by identifying the main user groups.
</display>
### 2. Primary User Segment Development
@ -150,12 +152,14 @@ Prepare the following structure for document append:
### 6. Present MENU OPTIONS
**Content Presentation:**
"I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
<display>
I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
**Here's what I'll add to the document:**
[Show the complete markdown content from step 5]
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>
#### Menu Handling Logic:

12
src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md
View File

@ -61,7 +61,8 @@ Define comprehensive success metrics that include user success, business objecti
### 1. Begin Success Metrics Discovery
**Opening Exploration:**
"Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
<display>
Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
**Success Discovery:**
@ -69,7 +70,8 @@ Define comprehensive success metrics that include user success, business objecti
- What would make users say 'this was worth it'?
- What metrics show we're creating real value?
Let's start with the user perspective."
Let's start with the user perspective.
</display>
### 2. User Success Metrics
@ -153,12 +155,14 @@ Prepare the following structure for document append:
### 7. Present MENU OPTIONS
**Content Presentation:**
"I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
<display>
I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
**Here's what I'll add to the document:**
[Show the complete markdown content from step 6]
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>
#### Menu Handling Logic:

12
src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md
View File

@ -61,7 +61,8 @@ Define MVP scope with clear boundaries and outline future vision through collabo
### 1. Begin Scope Definition
**Opening Exploration:**
"Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
<display>
Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
**Scope Discovery:**
@ -69,7 +70,8 @@ Define MVP scope with clear boundaries and outline future vision through collabo
- What features would make users say 'this solves my problem'?
- How do we balance ambition with getting something valuable to users quickly?
Let's start with the MVP mindset: what's the smallest version that creates real value?"
Let's start with the MVP mindset: what's the smallest version that creates real value?
</display>
### 2. MVP Core Features Definition
@ -167,12 +169,14 @@ Prepare the following structure for document append:
### 7. Present MENU OPTIONS
**Content Presentation:**
"I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
<display>
I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
**Here's what I'll add to the document:**
[Show the complete markdown content from step 6]
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>
#### Menu Handling Logic:

22
src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
View File

@ -56,22 +56,24 @@ Complete the product brief workflow, update status files, and provide guidance o
### 1. Announce Workflow Completion
**Completion Announcement:**
"🎉 **Product Brief Complete, {{user_name}}!**
<display>
**Product Brief Complete, {{user_name}}!**
I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
**What we've accomplished:**
- ✅ Executive Summary with clear vision and problem statement
- ✅ Core Vision with solution definition and unique differentiators
- ✅ Target Users with rich personas and user journeys
- ✅ Success Metrics with measurable outcomes and business objectives
- ✅ MVP Scope with focused feature set and clear boundaries
- ✅ Future Vision that inspires while maintaining current focus
- Executive Summary with clear vision and problem statement
- Core Vision with solution definition and unique differentiators
- Target Users with rich personas and user journeys
- Success Metrics with measurable outcomes and business objectives
- MVP Scope with focused feature set and clear boundaries
- Future Vision that inspires while maintaining current focus
**The complete Product Brief is now available at:** `{outputFile}`
This brief serves as the foundation for all subsequent product development activities and strategic decisions."
This brief serves as the foundation for all subsequent product development activities and strategic decisions.
</display>
### 2. Document Quality Check
@ -116,7 +118,9 @@ Provide guidance on logical next workflows:
### 4. Congrats to the user
"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
<display>
**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**
</display>
Recap that the brief captures everything needed to guide subsequent product development:

4
src/bmm/workflows/1-analysis/research/workflow.md
View File

@ -91,7 +91,8 @@ Execute research type discovery and routing:
### Collaborative Research Discovery
"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
<display>
Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
**Let me help you clarify what you'd like to research.**
@ -104,6 +105,7 @@ For example:
- 'AI implementation in financial services'
- 'Sustainable packaging regulations'
- 'Or anything else you have in mind...'
</display>
### Topic Exploration and Clarification

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md
View File

@ -176,7 +176,7 @@ Present the functional requirements for review, then display menu:
- Ask if they'd like to refine further, get other perspectives, or proceed
- Present menu options naturally as part of conversation
**What would you like to do?**"
**What would you like to do?**
<display>
**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Non-Functional Requirements (Step 10 of 11)

6
src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md
View File

@ -132,7 +132,7 @@ Display:
- Note: This hands off to the validation workflow which will run its complete 13-step process
- **IF E (Edit More):**
- Display: "**Additional Edits**"
- <display>**Additional Edits**</display>
- Ask: "What additional edits would you like to make?"
- Accept input, then display: "**Returning to edit step...**"
- Read fully and follow: step-e-03-edit.md again
@ -142,12 +142,12 @@ Display:
- Complete list of all changes made
- Before/after comparison (key improvements)
- Recommendations for next steps
- Display: "**Edit Workflow Complete**"
- <display>**Edit Workflow Complete**</display>
- Exit
- **IF X (Exit):**
- Display summary
- Display: "**Edit Workflow Complete**"
- <display>**Edit Workflow Complete**</display>
- Exit
- **IF Any other:** Help user, then redisplay menu

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

@ -94,7 +94,8 @@ Complete setup and report to user:
**Input Documents Discovered:**
Report what was found:
"Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
<display>
Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
**Documents Found:**
@ -106,7 +107,8 @@ Report what was found:
Do you have any other documents you'd like me to include, or shall we continue to the next step?
[C] Continue to UX discovery"
[C] Continue to UX discovery
</display>
## NEXT STEP:

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

@ -52,7 +52,8 @@ Reload the context documents listed in `inputDocuments`:
### 3. Summarize Current Progress
Welcome the user back and provide context:
"Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
<display>
Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
**Current Progress:**
@ -66,7 +67,8 @@ Welcome the user back and provide context:
- Current UX design document is ready with all completed sections
- Ready to continue from where we left off
Does this look right, or do you want to make any adjustments before we proceed?"
Does this look right, or do you want to make any adjustments before we proceed?
</display>
### 4. Determine Next Step
@ -81,9 +83,11 @@ Based on `lastStep` value, determine which step to load next:
### 5. Present Continuation Options
After presenting current progress, ask:
"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
<display>
Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
[C] Continue to Step {nextStepNumber}"
[C] Continue to Step {nextStepNumber}
</display>
## SUCCESS METRICS:
@ -106,7 +110,8 @@ After presenting current progress, ask:
## 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}}.
<display>
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}.
@ -118,7 +123,8 @@ Would you like me to:
- Suggest next workflow steps (like wireframe generation or architecture)
- Start a new UX design revision
What would be most helpful?"
What would be most helpful?
</display>
## NEXT STEP:

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

@ -51,7 +51,8 @@ Understand the project context, target users, and what makes this product specia
### 1. Review Loaded Context
Start by analyzing 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}}.
<display>
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}
@ -62,12 +63,14 @@ Start by analyzing what we know from the 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?"
Does this match your understanding? Are there any corrections or additions you'd like to make?
</display>
### 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:
<display>
Since we don't have complete documentation, let's start with the essentials:
**What are you building?** (Describe your product in 1-2 sentences)
@ -75,12 +78,14 @@ If no documents were loaded or key information is missing:
**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)"
**What's the main thing users will do with this?** (Core user action or goal)
</display>
### 3. Explore User Context Deeper
Dive into user understanding:
"Let me understand your users better to inform the UX design:
<display>
Let me understand your users better to inform the UX design:
**User Context Questions:**
@ -89,12 +94,14 @@ Dive into user understanding:
- 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?"
- When/where will they use this product?
</display>
### 4. Identify UX Design Challenges
Surface the key UX challenges to address:
"From what we've discussed, I'm seeing some key UX design considerations:
<display>
From what we've discussed, I'm seeing some key UX design considerations:
**Design Challenges:**
@ -107,7 +114,8 @@ Surface the key UX challenges to address:
- [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?"
Does this capture the key UX considerations we need to address?
</display>
### 5. Generate Project Understanding Content
@ -140,14 +148,16 @@ When saving to document, append these Level 2 and Level 3 sections:
### 6. Present Content and Menu
Show the generated project understanding content and present choices:
"I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
<display>
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?**
[C] Continue - Save this to the document and move to core experience definition"
[C] Continue - Save this to the document and move to core experience definition
</display>
### 7. Handle Menu Selection

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

@ -51,7 +51,8 @@ Define the core user experience, platform requirements, and what makes the inter
### 1. Define Core User Action
Start by identifying the most important user interaction:
"Now let's dig into the heart of the user experience for {{project_name}}.
<display>
Now let's dig into the heart of the user experience for {{project_name}}.
**Core Experience Questions:**
@ -60,12 +61,14 @@ Start by identifying the most important user interaction:
- 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."
Think about the core loop or primary action that defines your product's value.
</display>
### 2. Explore Platform Requirements
Determine where and how users will interact:
"Let's define the platform context for {{project_name}}:
<display>
Let's define the platform context for {{project_name}}:
**Platform Questions:**
@ -73,34 +76,40 @@ Determine where and how users will interact:
- 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?"
- Any device-specific capabilities we should leverage?
</display>
### 3. Identify Effortless Interactions
Surface what should feel magical or completely seamless:
"**Effortless Experience Design:**
<display>
**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?"
- Where can we eliminate steps that competitors require?
</display>
### 4. Define Critical Success Moments
Identify the moments that determine success or failure:
"**Critical Success Moments:**
<display>
**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?"
- Where does first-time user success happen?
</display>
### 5. Synthesize Experience Principles
Extract guiding principles from the conversation:
"Based on our discussion, I'm hearing these core experience principles for {{project_name}}:
<display>
Based on our discussion, I'm hearing these core experience principles for {{project_name}}:
**Experience Principles:**
@ -109,7 +118,8 @@ Extract guiding principles from the conversation:
- [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?"
These principles will guide all our UX decisions. Do these capture what's most important?
</display>
### 6. Generate Core Experience Content
@ -146,7 +156,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated core experience content and present choices:
"I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
<display>
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:**
@ -155,7 +166,8 @@ Show the generated core experience content and present choices:
**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
[C] Continue - Save this to the document and move to emotional response definition"
[C] Continue - Save this to the document and move to emotional response definition
</display>
### 8. Handle Menu Selection

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

@ -51,7 +51,8 @@ Define the desired emotional responses users should feel when using the product.
### 1. Explore Core Emotional Goals
Start by understanding the emotional objectives:
"Now let's think about how {{project_name}} should make users feel.
<display>
Now let's think about how {{project_name}} should make users feel.
**Emotional Response Questions:**
@ -60,23 +61,27 @@ Start by understanding the emotional objectives:
- 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?"
Common emotional goals: Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged?
</display>
### 2. Identify Emotional Journey Mapping
Explore feelings at different stages:
"**Emotional Journey Considerations:**
<display>
**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?"
- How should they feel when returning to use it again?
</display>
### 3. Define Micro-Emotions
Surface subtle but important emotional states:
"**Micro-Emotions to Consider:**
<display>
**Micro-Emotions to Consider:**
- Confidence vs. Confusion
- Trust vs. Skepticism
@ -85,12 +90,14 @@ Surface subtle but important emotional states:
- Delight vs. Satisfaction
- Belonging vs. Isolation
Which of these emotional states are most critical for your product's success?"
Which of these emotional states are most critical for your product's success?
</display>
### 4. Connect Emotions to UX Decisions
Link feelings to design implications:
"**Design Implications:**
<display>
**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?
@ -101,18 +108,21 @@ Link feelings to design implications:
- [Emotion 1] → [UX design approach]
- [Emotion 2] → [UX design approach]
- [Emotion 3] → [UX design approach]"
- [Emotion 3] → [UX design approach]
</display>
### 5. Validate Emotional Goals
Check if emotional goals align with product vision:
"Let me make sure I understand the emotional vision for {{project_name}}:
<display>
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?"
Does this capture the emotional experience you want to create? Any adjustments needed?
</display>
### 6. Generate Emotional Response Content
@ -149,7 +159,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated emotional response content and present choices:
"I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
<display>
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:**
@ -158,7 +169,8 @@ Show the generated emotional response content and present choices:
**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
[C] Continue - Save this to the document and move to inspiration analysis"
[C] Continue - Save this to the document and move to inspiration analysis
</display>
### 8. Handle Menu Selection

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

@ -51,7 +51,8 @@ Analyze inspiring products and UX patterns to inform design decisions for the cu
### 1. Identify User's Favorite Apps
Start by gathering inspiration sources:
"Let's learn from products your users already love and use regularly.
<display>
Let's learn from products your users already love and use regularly.
**Inspiration Questions:**
@ -60,12 +61,14 @@ Start by gathering inspiration sources:
- 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."
Think about apps in your category or even unrelated products that have great UX.
</display>
### 2. Analyze UX Patterns and Principles
Break down what makes these apps successful:
"For each inspiring app, let's analyze their UX success:
<display>
For each inspiring app, let's analyze their UX success:
**For [App Name]:**
@ -74,12 +77,14 @@ Break down what makes these apps successful:
- 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?"
- How do they handle errors or edge cases?
</display>
### 3. Extract Transferable Patterns
Identify patterns that could apply to your project:
"**Transferable UX Patterns:**
<display>
**Transferable UX Patterns:**
Looking across these inspiring apps, I see patterns we could adapt:
**Navigation Patterns:**
@ -97,24 +102,28 @@ Looking across these inspiring apps, I see patterns we could adapt:
- [Pattern 1] - supports your [emotional goal]
- [Pattern 2] - aligns with your [platform requirements]
Which of these patterns resonate most for your product?"
Which of these patterns resonate most for your product?
</display>
### 4. Identify Anti-Patterns to Avoid
Surface what not to do based on analysis:
"**UX Anti-Patterns to Avoid:**
<display>
**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."
Learning from others' mistakes is as important as learning from their successes.
</display>
### 5. Define Design Inspiration Strategy
Create a clear strategy for using this inspiration:
"**Design Inspiration Strategy:**
<display>
**Design Inspiration Strategy:**
**What to Adopt:**
@ -131,7 +140,8 @@ Create a clear strategy for using this inspiration:
- [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."
This strategy will guide our design decisions while keeping {{project_name}} unique.
</display>
### 6. Generate Inspiration Analysis Content
@ -164,7 +174,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated inspiration analysis content and present choices:
"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.
<display>
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:**
@ -173,7 +184,8 @@ Show the generated inspiration analysis content and present choices:
**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
[C] Continue - Save this to the document and move to design system choice"
[C] Continue - Save this to the document and move to design system choice
</display>
### 8. Handle Menu Selection

34
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md
View File

@ -51,7 +51,8 @@ Choose appropriate design system approach based on project requirements and cons
### 1. Present Design System Options
Educate about design system approaches:
"For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI - they provide proven components and patterns, ensuring consistency and speeding development.
<display>
For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI - they provide proven components and patterns, ensuring consistency and speeding development.
**Design System Approaches:**
@ -76,12 +77,14 @@ Educate about design system approaches:
- Moderate learning curve
- Good balance of speed and uniqueness
Which direction feels right for your project?"
Which direction feels right for your project?
</display>
### 2. Analyze Project Requirements
Guide decision based on project context:
"**Let's consider your specific needs:**
<display>
**Let's consider your specific needs:**
**Based on our previous conversations:**
@ -97,12 +100,14 @@ Guide decision based on project context:
- Brand guidelines or existing visual identity
- Team's design expertise
- Long-term maintenance considerations
- Integration requirements with existing systems"
- Integration requirements with existing systems
</display>
### 3. Explore Specific Design System Options
Dive deeper into relevant options:
"**Recommended Options Based on Your Needs:**
<display>
**Recommended Options Based on Your Needs:**
**For [Your Platform Type]:**
@ -117,12 +122,14 @@ Dive deeper into relevant options:
- Customization capabilities
- Accessibility compliance
- Performance characteristics
- Learning curve for your team"
- Learning curve for your team
</display>
### 4. Facilitate Decision Process
Help user make informed choice:
"**Decision Framework:**
<display>
**Decision Framework:**
1. What's most important: Speed, uniqueness, or balance?
2. How much design expertise does your team have?
@ -130,12 +137,14 @@ Help user make informed choice:
4. What's your timeline and budget?
5. Long-term maintenance needs?
Let's evaluate options based on your answers to these questions."
Let's evaluate options based on your answers to these questions.
</display>
### 5. Finalize Design System Choice
Confirm and document the decision:
"Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
<display>
Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
**Rationale:**
@ -149,7 +158,8 @@ Confirm and document the decision:
- Define component strategy for custom components needed
- Establish design tokens and patterns
Does this design system choice feel right to you?"
Does this design system choice feel right to you?
</display>
### 6. Generate Design System Content
@ -182,7 +192,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated design system content and present choices:
"I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
<display>
I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
**Here's what I'll add to the document:**
@ -192,6 +203,7 @@ Show the generated design system content and present choices:
[A] Advanced Elicitation - Let's refine our design system decision
[P] Party Mode - Bring technical perspectives on design systems
[C] Continue - Save this to the document and move to defining experience
</display>
### 8. Handle Menu Selection

34
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md
View File

@ -51,7 +51,8 @@ Define the core interaction that, if nailed, makes everything else follow in the
### 1. Identify the Defining Experience
Focus on the core interaction:
"Every successful product has a defining experience - the core interaction that, if we nail it, everything else follows.
<display>
Every successful product has a defining experience - the core interaction that, if we nail it, everything else follows.
**Think about these famous examples:**
@ -63,12 +64,14 @@ Focus on the core interaction:
**For {{project_name}}:**
What's the core action that users will describe to their friends?
What's the interaction that makes users feel successful?
If we get ONE thing perfectly right, what should it be?"
If we get ONE thing perfectly right, what should it be?
</display>
### 2. Explore the User's Mental Model
Understand how users think about the core task:
"**User Mental Model Questions:**
<display>
**User Mental Model Questions:**
- How do users currently solve this problem?
- What mental model do they bring to this task?
@ -79,12 +82,14 @@ Understand how users think about the core task:
- What do users love/hate about existing approaches?
- What shortcuts or workarounds do they use?
- What makes existing solutions feel magical or terrible?"
- What makes existing solutions feel magical or terrible?
</display>
### 3. Define Success Criteria for Core Experience
Establish what makes the core interaction successful:
"**Core Experience Success Criteria:**
<display>
**Core Experience Success Criteria:**
- What makes users say 'this just works'?
- When do they feel smart or accomplished?
@ -96,12 +101,14 @@ Establish what makes the core interaction successful:
- [Success indicator 1]
- [Success indicator 2]
- [Success indicator 3]"
- [Success indicator 3]
</display>
### 4. Identify Novel vs. Established Patterns
Determine if we need to innovate or can use proven patterns:
"**Pattern Analysis:**
<display>
**Pattern Analysis:**
Looking at your core experience, does this:
- Use established UX patterns that users already understand?
@ -118,12 +125,14 @@ Looking at your core experience, does this:
- Which proven patterns should we adopt?
- How can we innovate within familiar patterns?
- What's our unique twist on established interactions?"
- What's our unique twist on established interactions?
</display>
### 5. Define Experience Mechanics
Break down the core interaction into details:
"**Core Experience Mechanics:**
<display>
**Core Experience Mechanics:**
Let's design the step-by-step flow for [defining experience]:
**1. Initiation:**
@ -147,7 +156,8 @@ Let's design the step-by-step flow for [defining experience]:
- How do users know they're done?
- What's the successful outcome?
- What's next?"
- What's next?
</display>
### 6. Generate Defining Experience Content
@ -184,7 +194,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated defining experience content and present choices:
"I've defined the core experience for {{project_name}} - the interaction that will make users love this product.
<display>
I've defined the core experience for {{project_name}} - the interaction that will make users love this product.
**Here's what I'll add to the document:**
@ -194,6 +205,7 @@ Show the generated defining experience content and present choices:
[A] Advanced Elicitation - Let's refine the core experience definition
[P] Party Mode - Bring different perspectives on the defining interaction
[C] Continue - Save this to the document and move to visual foundation
</display>
### 8. Handle Menu Selection

34
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md
View File

@ -51,24 +51,29 @@ Establish the visual design foundation including color themes, typography, and s
### 1. Brand Guidelines Assessment
Check for existing brand requirements:
"Do you have existing brand guidelines or a specific color palette I should follow? (y/n)
<display>
Do you have existing brand guidelines or a specific color palette I should follow? (y/n)
If yes, I'll extract and document your brand colors and create semantic color mappings.
If no, I'll generate theme options based on your project's personality and emotional goals from our earlier discussion."
If no, I'll generate theme options based on your project's personality and emotional goals from our earlier discussion.
</display>
### 2. Generate Color Theme Options (If no brand guidelines)
Create visual exploration opportunities:
"If no existing brand guidelines, I'll create a color theme visualizer to help you explore options.
<display>
If no existing brand guidelines, I'll create a color theme visualizer to help you explore options.
🎨 I can generate comprehensive HTML color theme visualizers with multiple theme options, complete UI examples, and the ability to see how colors work in real interface contexts.
This will help you make an informed decision about the visual direction for {{project_name}}."
This will help you make an informed decision about the visual direction for {{project_name}}.
</display>
### 3. Define Typography System
Establish the typographic foundation:
"**Typography Questions:**
<display>
**Typography Questions:**
- What should the overall tone feel like? (Professional, friendly, modern, classic?)
- How much text content will users read? (Headings only? Long-form content?)
@ -80,12 +85,14 @@ Establish the typographic foundation:
- Choose primary and secondary typefaces
- Establish type scale (h1, h2, h3, body, etc.)
- Define line heights and spacing relationships
- Consider readability and accessibility"
- Consider readability and accessibility
</display>
### 4. Establish Spacing and Layout Foundation
Define the structural foundation:
"**Spacing and Layout Foundation:**
<display>
**Spacing and Layout Foundation:**
- How should the overall layout feel? (Dense and efficient? Airy and spacious?)
- What spacing unit should we use? (4px, 8px, 12px base?)
@ -96,12 +103,14 @@ Define the structural foundation:
- [Layout principle 1 based on product type]
- [Layout principle 2 based on user needs]
- [Layout principle 3 based on platform requirements]"
- [Layout principle 3 based on platform requirements]
</display>
### 5. Create Visual Foundation Strategy
Synthesize all visual decisions:
"**Visual Foundation Strategy:**
<display>
**Visual Foundation Strategy:**
**Color System:**
@ -121,7 +130,8 @@ Synthesize all visual decisions:
- Grid system approach
- Component spacing relationships
This foundation will ensure consistency across all our design decisions."
This foundation will ensure consistency across all our design decisions.
</display>
### 6. Generate Visual Foundation Content
@ -154,7 +164,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated visual foundation content and present choices:
"I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design.
<display>
I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design.
**Here's what I'll add to the document:**
@ -164,6 +175,7 @@ Show the generated visual foundation content and present choices:
[A] Advanced Elicitation - Let's refine our visual foundation
[P] Party Mode - Bring design perspectives on visual choices
[C] Continue - Save this to the document and move to design directions
</display>
### 8. Handle Menu Selection

34
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md
View File

@ -51,7 +51,8 @@ Generate comprehensive design direction mockups showing different visual approac
### 1. Generate Design Direction Variations
Create diverse visual explorations:
"I'll generate 6-8 different design direction variations exploring:
<display>
I'll generate 6-8 different design direction variations exploring:
- Different layout approaches and information hierarchy
- Various interaction patterns and visual weights
@ -59,12 +60,14 @@ Create diverse visual explorations:
- Different density and spacing approaches
- Various navigation and component arrangements
Each mockup will show a complete vision for {{project_name}} with all our design decisions applied."
Each mockup will show a complete vision for {{project_name}} with all our design decisions applied.
</display>
### 2. Create HTML Design Direction Showcase
Generate interactive visual exploration:
"🎨 Design Direction Mockups Generated!
<display>
🎨 Design Direction Mockups Generated!
I'm creating a comprehensive HTML design direction showcase at `{planning_artifacts}/ux-design-directions.html`
@ -76,12 +79,14 @@ I'm creating a comprehensive HTML design direction showcase at `{planning_artifa
- Complete UI examples with real content
- Responsive behavior demonstrations
Each mockup represents a complete visual direction for your app's look and feel."
Each mockup represents a complete visual direction for your app's look and feel.
</display>
### 3. Present Design Exploration Framework
Guide evaluation criteria:
"As you explore the design directions, look for:
<display>
As you explore the design directions, look for:
✅ **Layout Intuitiveness** - Which information hierarchy matches your priorities?
✅ **Interaction Style** - Which interaction style fits your core experience?
@ -90,12 +95,14 @@ Guide evaluation criteria:
✅ **Component Usage** - How well do the components support your user journeys?
✅ **Brand Alignment** - Which direction best supports your emotional goals?
Take your time exploring - this is a crucial decision that will guide all our design work!"
Take your time exploring - this is a crucial decision that will guide all our design work!
</display>
### 4. Facilitate Design Direction Selection
Help user choose or combine elements:
"After exploring all the design directions:
<display>
After exploring all the design directions:
**Which approach resonates most with you?**
@ -109,19 +116,22 @@ Help user choose or combine elements:
- Which layout feels most intuitive for your users?
- Which visual weight matches your brand personality?
- Which interaction style supports your core experience?
- Are there elements from different directions you'd like to combine?"
- Are there elements from different directions you'd like to combine?
</display>
### 5. Document Design Direction Decision
Capture the chosen approach:
"Based on your exploration, I'm understanding your design direction preference:
<display>
Based on your exploration, I'm understanding your design direction preference:
**Chosen Direction:** [Direction number or combination]
**Key Elements:** [Specific elements you liked]
**Modifications Needed:** [Any changes requested]
**Rationale:** [Why this direction works for your product]
This will become our design foundation moving forward. Are we ready to lock this in, or do you want to explore variations?"
This will become our design foundation moving forward. Are we ready to lock this in, or do you want to explore variations?
</display>
### 6. Generate Design Direction Content
@ -154,7 +164,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated design direction content and present choices:
"I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work.
<display>
I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work.
**Here's what I'll add to the document:**
@ -164,6 +175,7 @@ Show the generated design direction content and present choices:
[A] Advanced Elicitation - Let's refine our design direction
[P] Party Mode - Bring different perspectives on visual choices
[C] Continue - Save this to the document and move to user journey flows
</display>
### 8. Handle Menu Selection

34
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md
View File

@ -51,7 +51,8 @@ Design detailed user journey flows for critical user interactions.
### 1. Load PRD User Journeys as Foundation
Start with user journeys already defined in the PRD:
"Great! Since we have the PRD available, let's build on the user journeys already documented there.
<display>
Great! Since we have the PRD available, let's build on the user journeys already documented there.
**Existing User Journeys from PRD:**
I've already loaded these user journeys from your PRD:
@ -66,14 +67,16 @@ Looking at the PRD journeys, I need to design detailed interaction flows for:
- [Critical journey 2 identified from PRD narratives]
- [Critical journey 3 identified from PRD narratives]
The PRD gave us the stories - now we design the mechanics!"
The PRD gave us the stories - now we design the mechanics!
</display>
### 2. Design Each Journey Flow
For each critical journey, design detailed flow:
**For [Journey Name]:**
"Let's design the flow for users accomplishing [journey goal].
<display>
Let's design the flow for users accomplishing [journey goal].
**Flow Design Questions:**
@ -83,12 +86,14 @@ For each critical journey, design detailed flow:
- How do they know they're progressing successfully?
- What does success look like for this journey?
- Where might they get confused or stuck?
- How do they recover from errors?"
- How do they recover from errors?
</display>
### 3. Create Flow Diagrams
Visualize each journey with Mermaid diagrams:
"I'll create detailed flow diagrams for each journey showing:
<display>
I'll create detailed flow diagrams for each journey showing:
**[Journey Name] Flow:**
@ -98,12 +103,14 @@ Visualize each journey with Mermaid diagrams:
- Error recovery mechanisms
- Progressive disclosure of information
Each diagram will map the complete user experience from start to finish."
Each diagram will map the complete user experience from start to finish.
</display>
### 4. Optimize for Efficiency and Delight
Refine flows for optimal user experience:
"**Flow Optimization:**
<display>
**Flow Optimization:**
For each journey, let's ensure we're:
- Minimizing steps to value (getting users to success quickly)
@ -116,12 +123,14 @@ For each journey, let's ensure we're:
- [Optimization 1 for journey efficiency]
- [Optimization 2 for user delight]
- [Optimization 3 for error handling]"
- [Optimization 3 for error handling]
</display>
### 5. Document Journey Patterns
Extract reusable patterns across journeys:
"**Journey Patterns:**
<display>
**Journey Patterns:**
Across these flows, I'm seeing some common patterns we can standardize:
**Navigation Patterns:**
@ -139,7 +148,8 @@ Across these flows, I'm seeing some common patterns we can standardize:
- [Feedback pattern 1]
- [Feedback pattern 2]
These patterns will ensure consistency across all user experiences."
These patterns will ensure consistency across all user experiences.
</display>
### 6. Generate User Journey Content
@ -172,7 +182,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated user journey content and present choices:
"I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction.
<display>
I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction.
**Here's what I'll add to the document:**
@ -182,6 +193,7 @@ Show the generated user journey content and present choices:
[A] Advanced Elicitation - Let's refine our user journey designs
[P] Party Mode - Bring different perspectives on user flows
[C] Continue - Save this to the document and move to component strategy
</display>
### 8. Handle Menu Selection

28
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md
View File

@ -51,7 +51,8 @@ Define component library strategy and design custom components not covered by th
### 1. Analyze Design System Coverage
Review what components are available vs. needed:
"Based on our chosen design system [design system from step 6], let's identify what components are already available and what we need to create custom.
<display>
Based on our chosen design system [design system from step 6], let's identify what components are already available and what we need to create custom.
**Available from Design System:**
[List of components available in chosen design system]
@ -66,14 +67,16 @@ Looking at our user journeys and design direction, we need:
**Gap Analysis:**
- [Gap 1 - needed but not available]
- [Gap 2 - needed but not available]"
- [Gap 2 - needed but not available]
</display>
### 2. Design Custom Components
For each custom component needed, design thoroughly:
**For each custom component:**
"**[Component Name] Design:**
<display>
**[Component Name] Design:**
**Purpose:** What does this component do for users?
**Content:** What information or data does it display?
@ -82,7 +85,8 @@ For each custom component needed, design thoroughly:
**Variants:** Are there different sizes or styles needed?
**Accessibility:** What ARIA labels and keyboard support needed?
Let's walk through each custom component systematically."
Let's walk through each custom component systematically.
</display>
### 3. Document Component Specifications
@ -106,7 +110,8 @@ Create detailed specifications for each component:
### 4. Define Component Strategy
Establish overall component library approach:
"**Component Strategy:**
<display>
**Component Strategy:**
**Foundation Components:** (from design system)
@ -123,12 +128,14 @@ Establish overall component library approach:
- Build custom components using design system tokens
- Ensure consistency with established patterns
- Follow accessibility best practices
- Create reusable patterns for common use cases"
- Create reusable patterns for common use cases
</display>
### 5. Plan Implementation Roadmap
Define how and when to build components:
"**Implementation Roadmap:**
<display>
**Implementation Roadmap:**
**Phase 1 - Core Components:**
@ -145,7 +152,8 @@ Define how and when to build components:
- [Component 5] - optimizes [user journey]
- [Component 6] - adds [special feature]
This roadmap helps prioritize development based on user journey criticality."
This roadmap helps prioritize development based on user journey criticality.
</display>
### 6. Generate Component Strategy Content
@ -178,7 +186,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated component strategy content and present choices:
"I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
<display>
I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
**Here's what I'll add to the document:**
@ -188,6 +197,7 @@ Show the generated component strategy content and present choices:
[A] Advanced Elicitation - Let's refine our component strategy
[P] Party Mode - Bring technical perspectives on component design
[C] Continue - Save this to the document and move to UX patterns
</display>
### 8. Handle Menu Selection

22
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md
View File

@ -51,7 +51,8 @@ Establish UX consistency patterns for common situations like buttons, forms, nav
### 1. Identify Pattern Categories
Determine which patterns need definition for your product:
"Let's establish consistency patterns for how {{project_name}} behaves in common situations.
<display>
Let's establish consistency patterns for how {{project_name}} behaves in common situations.
**Pattern Categories to Define:**
@ -63,14 +64,16 @@ Determine which patterns need definition for your product:
- Empty states and loading states
- Search and filtering patterns
Which categories are most critical for your product? We can go through each thoroughly or focus on the most important ones."
Which categories are most critical for your product? We can go through each thoroughly or focus on the most important ones.
</display>
### 2. Define Critical Patterns First
Focus on patterns most relevant to your product:
**For [Critical Pattern Category]:**
"**[Pattern Type] Patterns:**
<display>
**[Pattern Type] Patterns:**
What should users see/do when they need to [pattern action]?
**Considerations:**
@ -86,7 +89,8 @@ What should users see/do when they need to [pattern action]?
- [Example 1 for this pattern type]
- [Example 2 for this pattern type]
How should {{project_name}} handle [pattern type] interactions?"
How should {{project_name}} handle [pattern type] interactions?
</display>
### 3. Establish Pattern Guidelines
@ -108,7 +112,8 @@ Document specific design decisions:
### 4. Design System Integration
Ensure patterns work with chosen design system:
"**Integration with [Design System]:**
<display>
**Integration with [Design System]:**
- How do these patterns complement our design system components?
- What customizations are needed?
@ -118,7 +123,8 @@ Ensure patterns work with chosen design system:
- [Custom rule 1]
- [Custom rule 2]
- [Custom rule 3]"
- [Custom rule 3]
</display>
### 5. Create Pattern Documentation
@ -167,7 +173,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated UX patterns content and present choices:
"I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions.
<display>
I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions.
**Here's what I'll add to the document:**
@ -177,6 +184,7 @@ Show the generated UX patterns content and present choices:
[A] Advanced Elicitation - Let's refine our UX patterns
[P] Party Mode - Bring different perspectives on consistency patterns
[C] Continue - Save this to the document and move to responsive design
</display>
### 8. Handle Menu Selection

34
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md
View File

@ -51,7 +51,8 @@ Define responsive design strategy and accessibility requirements for the product
### 1. Define Responsive Strategy
Establish how the design adapts across devices:
"Let's define how {{project_name}} adapts across different screen sizes and devices.
<display>
Let's define how {{project_name}} adapts across different screen sizes and devices.
**Responsive Design Questions:**
@ -71,12 +72,14 @@ Establish how the design adapts across devices:
- Bottom navigation or hamburger menu?
- How do layouts collapse on small screens?
- What's the most critical information to show mobile-first?"
- What's the most critical information to show mobile-first?
</display>
### 2. Establish Breakpoint Strategy
Define when and how layouts change:
"**Breakpoint Strategy:**
<display>
**Breakpoint Strategy:**
We need to define screen size breakpoints where layouts adapt.
**Common Breakpoints:**
@ -89,12 +92,14 @@ We need to define screen size breakpoints where layouts adapt.
- Use standard breakpoints or custom ones?
- Focus on mobile-first or desktop-first design?
- Have specific breakpoints for your key use cases?"
- Have specific breakpoints for your key use cases?
</display>
### 3. Design Accessibility Strategy
Define accessibility requirements and compliance level:
"**Accessibility Strategy:**
<display>
**Accessibility Strategy:**
What level of WCAG compliance does {{project_name}} need?
**WCAG Levels:**
@ -113,12 +118,14 @@ What level of WCAG compliance does {{project_name}} need?
- Keyboard navigation support
- Screen reader compatibility
- Touch target sizes (minimum 44x44px)
- Focus indicators and skip links"
- Focus indicators and skip links
</display>
### 4. Define Testing Strategy
Plan how to ensure responsive design and accessibility:
"**Testing Strategy:**
<display>
**Testing Strategy:**
**Responsive Testing:**
@ -137,12 +144,14 @@ Plan how to ensure responsive design and accessibility:
- Include users with disabilities in testing
- Test with diverse assistive technologies
- Validate with actual target devices"
- Validate with actual target devices
</display>
### 5. Document Implementation Guidelines
Create specific guidelines for developers:
"**Implementation Guidelines:**
<display>
**Implementation Guidelines:**
**Responsive Development:**
@ -157,7 +166,8 @@ Create specific guidelines for developers:
- ARIA labels and roles
- Keyboard navigation implementation
- Focus management and skip links
- High contrast mode support"
- High contrast mode support
</display>
### 6. Generate Responsive & Accessibility Content
@ -194,7 +204,8 @@ When saving to document, append these Level 2 and Level 3 sections:
### 7. Present Content and Menu
Show the generated responsive and accessibility content and present choices:
"I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users.
<display>
I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users.
**Here's what I'll add to the document:**
@ -204,6 +215,7 @@ Show the generated responsive and accessibility content and present choices:
[A] Advanced Elicitation - Let's refine our responsive/accessibility strategy
[P] Party Mode - Bring different perspectives on inclusive design
[C] Continue - Save this to the document and complete the workflow
</display>
### 8. Handle Menu Selection

6
src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
View File

@ -44,7 +44,8 @@ Complete the UX design workflow, update status files, and suggest next steps for
### 1. Announce Workflow Completion
Inform user that the UX design is complete:
"🎉 **UX Design Complete, {{user_name}}!**
<display>
🎉 **UX Design Complete, {{user_name}}!**
I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}.
@ -69,7 +70,8 @@ I've successfully collaborated with you to create a comprehensive UX design spec
- Color themes visualizer: `{planning_artifacts}/ux-color-themes.html`
- Design directions mockups: `{planning_artifacts}/ux-design-directions.html`
This specification is now ready to guide visual design, implementation, and development."
This specification is now ready to guide visual design, implementation, and development.
</display>
### 2. Workflow Status Update

12
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md
View File

@ -54,14 +54,16 @@ To discover, inventory, and organize all project documents, identifying duplicat
### 1. Initialize Document Discovery
"Beginning **Document Discovery** to inventory all project files.
<display>
Beginning **Document Discovery** to inventory all project files.
I will:
1. Search for all required documents (PRD, Architecture, Epics, UX)
2. Group sharded documents together
3. Identify any duplicates (whole + sharded versions)
4. Present findings for your confirmation"
4. Present findings for your confirmation
</display>
### 2. Document Search Patterns
@ -133,7 +135,8 @@ Initialize {outputFile} with {templateFile}.
### 6. Present Findings and Get Confirmation
Display findings and ask:
"**Document Discovery Complete**
<display>
**Document Discovery Complete**
[Show organized file list]
@ -147,7 +150,8 @@ Display findings and ask:
- If duplicates exist: Please remove/rename one version
- Confirm which documents to use for assessment
**Ready to proceed?** [C] Continue after resolving issues"
**Ready to proceed?** [C] Continue after resolving issues
</display>
### 7. Present MENU OPTIONS

6
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md
View File

@ -54,7 +54,8 @@ To fully read and analyze the PRD document (whole or sharded) to extract all Fun
### 1. Initialize PRD Analysis
"Beginning **PRD Analysis** to extract all requirements.
<display>
Beginning **PRD Analysis** to extract all requirements.
I will:
@ -62,7 +63,8 @@ I will:
2. Read it completely and thoroughly
3. Extract ALL Functional Requirements (FRs)
4. Extract ALL Non-Functional Requirements (NFRs)
5. Document findings for coverage validation"
5. Document findings for coverage validation
</display>
### 2. Load and Read PRD

6
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md
View File

@ -53,14 +53,16 @@ To validate that all Functional Requirements from the PRD are captured in the ep
### 1. Initialize Coverage Validation
"Beginning **Epic Coverage Validation**.
<display>
Beginning **Epic Coverage Validation**.
I will:
1. Load the epics and stories document
2. Extract FR coverage information
3. Compare against PRD FRs from previous step
4. Identify any FRs not covered in epics"
4. Identify any FRs not covered in epics
</display>
### 2. Load Epics Document

6
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md
View File

@ -53,13 +53,15 @@ To check if UX documentation exists and validate that it aligns with PRD require
### 1. Initialize UX Validation
"Beginning **UX Alignment** validation.
<display>
Beginning **UX Alignment** validation.
I will:
1. Check if UX documentation exists
2. If UX exists: validate alignment with PRD and Architecture
3. If no UX: determine if UX is implied and document warning"
3. If no UX: determine if UX is implied and document warning
</display>
### 2. Search for UX Documentation

6
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md
View File

@ -55,7 +55,8 @@ To validate epics and stories against the best practices defined in create-epics
### 1. Initialize Best Practices Validation
"Beginning **Epic Quality Review** against create-epics-and-stories standards.
<display>
Beginning **Epic Quality Review** against create-epics-and-stories standards.
I will rigorously validate:
@ -64,7 +65,8 @@ I will rigorously validate:
- Story dependencies (no forward references)
- Proper story sizing and completeness
Any deviation from best practices will be flagged as a defect."
Any deviation from best practices will be flagged as a defect.
</display>
### 2. Epic Structure Validation

12
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
View File

@ -52,14 +52,16 @@ To provide a comprehensive summary of all findings and give the report a final p
### 1. Initialize Final Assessment
"Completing **Final Assessment**.
<display>
Completing **Final Assessment**.
I will now:
1. Review all findings from previous steps
2. Provide a comprehensive summary
3. Add specific recommendations
4. Determine overall readiness status"
4. Determine overall readiness status
</display>
### 2. Review Previous Findings
@ -105,11 +107,13 @@ This assessment identified [X] issues across [Y] categories. Address the critica
### 5. Present Completion
Display:
"**Implementation Readiness Assessment Complete**
<display>
**Implementation Readiness Assessment Complete**
Report generated: {outputFile}
The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."
The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations.
</display>
## WORKFLOW COMPLETE

4
src/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md
View File

@ -108,7 +108,8 @@ Complete setup and report to user:
**Input Documents Discovered:**
Report what was found:
"Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}.
<display>
Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}.
**Documents Found:**
@ -123,6 +124,7 @@ Report what was found:
Ready to begin architectural decision making. Do you have any other documents you'd like me to include?
[C] Continue to project context analysis
</display>
## SUCCESS METRICS:

5
src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md
View File

@ -55,7 +55,8 @@ Read the existing architecture document completely and analyze:
Show the user their current progress:
"Welcome back {{user_name}}! I found your Architecture work for {{project_name}}.
<display>
Welcome back {{user_name}}! I found your Architecture work for {{project_name}}.
**Current Progress:**
@ -77,7 +78,7 @@ Show the user their current progress:
[C] Continue to next logical step
[O] Overview of all remaining steps
[X] Start over (will overwrite existing work)
"
</display>
### 3. Handle User Choice

12
src/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md
View File

@ -94,7 +94,8 @@ Calculate and present project complexity:
Present your analysis back to user for validation:
"I'm reviewing your project documentation for {{project_name}}.
<display>
I'm reviewing your project documentation for {{project_name}}.
{if_epics_loaded}I see {{epic_count}} epics with {{story_count}} total stories.{/if_epics_loaded}
{if_no_epics}I found {{fr_count}} functional requirements organized into {{fr_category_list}}.{/if_no_epics}
@ -116,7 +117,8 @@ Present your analysis back to user for validation:
This analysis will help me guide you through the architectural decisions needed to ensure AI agents implement this consistently.
Does this match your understanding of the project scope and requirements?"
Does this match your understanding of the project scope and requirements?
</display>
### 4. Generate Project Context Content
@ -155,7 +157,8 @@ Prepare the content to append to the document:
Show the generated content and present choices:
"I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions.
<display>
I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions.
**Here's what I'll add to the document:**
@ -164,7 +167,8 @@ Show the generated content and present choices:
**What would you like to do?**
[A] Advanced Elicitation - Let's dive deeper into architectural implications
[P] Party Mode - Bring different perspectives to analyze requirements
[C] Continue - Save this analysis and begin architectural decisions"
[C] Continue - Save this analysis and begin architectural decisions
</display>
### 6. Handle Menu Selection

36
src/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md
View File

@ -53,7 +53,8 @@ Discover technical preferences and evaluate starter template options, leveraging
### 0. Check Technical Preferences & Context
**Check Project Context for Existing Technical Preferences:**
"Before we dive into starter templates, let me check if you have any technical preferences already documented.
<display>
Before we dive into starter templates, let me check if you have any technical preferences already documented.
{{if_project_context_exists}}
I found some technical rules in your project context file:
@ -68,10 +69,12 @@ I found some technical rules in your project context file:
{{else}}
No existing technical preferences found in project context file. We'll establish your technical preferences now.
{{/if_project_context}}"
{{/if_project_context}}
</display>
**Discover User Technical Preferences:**
"Based on your project context, let's discuss your technical preferences:
<display>
Based on your project context, let's discuss your technical preferences:
{{primary_technology_category}} Preferences:
@ -94,7 +97,8 @@ No existing technical preferences found in project context file. We'll establish
- Any existing systems or APIs you need to integrate with?
- Third-party services you plan to use (payment, authentication, analytics, etc.)?
These preferences will help me recommend the most suitable starter templates and guide our architectural decisions."
These preferences will help me recommend the most suitable starter templates and guide our architectural decisions.
</display>
### 1. Identify Primary Technology Domain
@ -173,28 +177,34 @@ For each viable starter option, document:
Based on user skill level and project needs:
**For Expert Users:**
"Found {{starter_name}} which provides:
<display>
Found {{starter_name}} which provides:
{{quick_decision_list_of_key_decisions}}
This would establish our base architecture with these technical decisions already made. Use it?"
This would establish our base architecture with these technical decisions already made. Use it?
</display>
**For Intermediate Users:**
"I found {{starter_name}}, which is a well-maintained starter for {{project_type}} projects.
<display>
I found {{starter_name}}, which is a well-maintained starter for {{project_type}} projects.
It makes these architectural decisions for us:
{{decision_list_with_explanations}}
This gives us a solid foundation following current best practices. Should we use it?"
This gives us a solid foundation following current best practices. Should we use it?
</display>
**For Beginner Users:**
"I found {{starter_name}}, which is like a pre-built foundation for your project.
<display>
I found {{starter_name}}, which is like a pre-built foundation for your project.
Think of it like buying a prefab house frame instead of cutting each board yourself.
It makes these decisions for us:
{{friendly_explanation_of_decisions}}
This is a great starting point that follows best practices and saves us from making dozens of small technical choices. Should we use it?"
This is a great starting point that follows best practices and saves us from making dozens of small technical choices. Should we use it?
</display>
### 7. Get Current CLI Commands
@ -262,7 +272,8 @@ Prepare the content to append to the document:
Show the generated content and present choices:
"I've analyzed starter template options for {{project_type}} projects.
<display>
I've analyzed starter template options for {{project_type}} projects.
**Here's what I'll add to the document:**
@ -271,7 +282,8 @@ Show the generated content and present choices:
**What would you like to do?**
[A] Advanced Elicitation - Explore custom approaches or unconventional starters
[P] Party Mode - Evaluate trade-offs from different perspectives
[C] Continue - Save this decision and move to architectural decisions"
[C] Continue - Save this decision and move to architectural decisions
</display>
### 10. Handle Menu Selection

40
src/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md
View File

@ -55,7 +55,8 @@ Facilitate collaborative architectural decision making, leveraging existing tech
### 1. Load Decision Framework & Check Existing Preferences
**Review Technical Preferences from Step 3:**
"Based on our technical preferences discussion in step 3, let's build on those foundations:
<display>
Based on our technical preferences discussion in step 3, let's build on those foundations:
**Your Technical Preferences:**
{{user_technical_preferences_from_step_3}}
@ -64,7 +65,8 @@ Facilitate collaborative architectural decision making, leveraging existing tech
{{starter_template_decisions}}
**Project Context Technical Rules:**
{{project_context_technical_rules}}"
{{project_context_technical_rules}}
</display>
**Identify Remaining Decisions:**
Based on technical preferences, starter template choice, and project context, identify remaining critical decisions:
@ -129,24 +131,29 @@ For each category, facilitate collaborative decision making:
Based on user skill level and project context:
**Expert Mode:**
"{{Decision_Category}}: {{Specific_Decision}}
<display>
{{Decision_Category}}: {{Specific_Decision}}
Options: {{concise_option_list_with_tradeoffs}}
What's your preference for this decision?"
What's your preference for this decision?
</display>
**Intermediate Mode:**
"Next decision: {{Human_Friendly_Category}}
<display>
Next decision: {{Human_Friendly_Category}}
We need to choose {{Specific_Decision}}.
Common options:
{{option_list_with_brief_explanations}}
For your project, I'd lean toward {{recommendation}} because {{reason}}. What are your thoughts?"
For your project, I'd lean toward {{recommendation}} because {{reason}}. What are your thoughts?
</display>
**Beginner Mode:**
"Let's talk about {{Human_Friendly_Category}}.
<display>
Let's talk about {{Human_Friendly_Category}}.
{{Educational_Context_About_Why_This_Matters}}
@ -158,7 +165,8 @@ Your main options:
My suggestion: {{recommendation}}
This is good for you because {{beginner_friendly_reason}}.
What feels right to you?"
What feels right to you?
</display>
**Verify Technology Versions:**
If decision involves specific technology:
@ -170,7 +178,9 @@ Search the web: "{{technology}} production readiness"
```
**Get User Input:**
"What's your preference? (or 'explain more' for details)"
<display>
What's your preference? (or 'explain more' for details)
</display>
**Handle User Response:**
@ -191,10 +201,12 @@ Search the web: "{{technology}} production readiness"
After each major decision, identify related decisions:
"This choice means we'll also need to decide:
<display>
This choice means we'll also need to decide:
- {{related_decision_1}}
- {{related_decision_2}}"
- {{related_decision_2}}
</display>
### 5. Generate Decisions Content
@ -249,7 +261,8 @@ After facilitating all decision categories, prepare the content to append:
Show the generated decisions content and present choices:
"I've documented all the core architectural decisions we've made together.
<display>
I've documented all the core architectural decisions we've made together.
**Here's what I'll add to the document:**
@ -258,7 +271,8 @@ Show the generated decisions content and present choices:
**What would you like to do?**
[A] Advanced Elicitation - Explore innovative approaches to any specific decisions
[P] Party Mode - Review decisions from multiple perspectives
[C] Continue - Save these decisions and move to implementation patterns"
[C] Continue - Save these decisions and move to implementation patterns
</display>
### 7. Handle Menu Selection

22
src/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md
View File

@ -99,23 +99,29 @@ Based on the chosen technology stack and decisions, identify where AI agents cou
For each conflict category, facilitate collaborative pattern definition:
**Present the Conflict Point:**
"Given that we're using {{tech_stack}}, different AI agents might handle {{conflict_area}} differently.
<display>
Given that we're using {{tech_stack}}, different AI agents might handle {{conflict_area}} differently.
For example, one agent might name database tables 'users' while another uses 'Users' - this would cause conflicts.
We need to establish consistent patterns that all agents follow."
We need to establish consistent patterns that all agents follow.
</display>
**Show Options and Trade-offs:**
"Common approaches for {{pattern_category}}:
<display>
Common approaches for {{pattern_category}}:
1. {{option_1}} - {{pros_and_cons}}
2. {{option_2}} - {{pros_and_cons}}
3. {{option_3}} - {{pros_and_cons}}
Which approach makes the most sense for our project?"
Which approach makes the most sense for our project?
</display>
**Get User Decision:**
"What's your preference for this pattern? (or discuss the trade-offs more)"
<display>
What's your preference for this pattern? (or discuss the trade-offs more)
</display>
### 3. Define Pattern Categories
@ -290,7 +296,8 @@ Prepare the content to append to the document:
Show the generated patterns content and present choices:
"I've documented implementation patterns that will prevent conflicts between AI agents working on this project.
<display>
I've documented implementation patterns that will prevent conflicts between AI agents working on this project.
**Here's what I'll add to the document:**
@ -299,7 +306,8 @@ Show the generated patterns content and present choices:
**What would you like to do?**
[A] Advanced Elicitation - Explore additional consistency patterns
[P] Party Mode - Review patterns from different implementation perspectives
[C] Continue - Save these patterns and move to project structure"
[C] Continue - Save these patterns and move to project structure
</display>
### 6. Handle Menu Selection

26
src/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md
View File

@ -55,14 +55,18 @@ Define the complete project structure and architectural boundaries based on all
Map project requirements to architectural components:
**From Epics (if available):**
"Epic: {{epic_name}} → Lives in {{module/directory/service}}"
<display>
Epic: {{epic_name}} → Lives in {{module/directory/service}}
</display>
- User stories within the epic
- Cross-epic dependencies
- Shared components needed
**From FR Categories (if no epics):**
"FR Category: {{fr_category_name}} → Lives in {{module/directory/service}}"
<display>
FR Category: {{fr_category_name}} → Lives in {{module/directory/service}}
</display>
- Related functional requirements
- Shared functionality across categories
@ -214,22 +218,26 @@ project-name/
Create explicit mapping from project requirements to specific files/directories:
**Epic/Feature Mapping:**
"Epic: User Management
<display>
Epic: User Management
- Components: src/components/features/users/
- Services: src/services/users/
- API Routes: src/app/api/users/
- Database: prisma/migrations/_*users*_
- Tests: tests/features/users/"
- Tests: tests/features/users/
</display>
**Cross-Cutting Concerns:**
"Authentication System
<display>
Authentication System
- Components: src/components/auth/
- Services: src/services/auth/
- Middleware: src/middleware/auth.ts
- Guards: src/guards/auth.guard.ts
- Tests: tests/auth/"
- Tests: tests/auth/
</display>
### 6. Generate Structure Content
@ -310,7 +318,8 @@ Prepare the content to append to the document:
Show the generated project structure content and present choices:
"I've created a complete project structure based on all our architectural decisions.
<display>
I've created a complete project structure based on all our architectural decisions.
**Here's what I'll add to the document:**
@ -319,7 +328,8 @@ Show the generated project structure content and present choices:
**What would you like to do?**
[A] Advanced Elicitation - Explore innovative project organization approaches
[P] Party Mode - Review structure from different development perspectives
[C] Continue - Save this structure and move to architecture validation"
[C] Continue - Save this structure and move to architecture validation
</display>
### 8. Handle Menu Selection

22
src/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md
View File

@ -155,25 +155,31 @@ Identify and document any missing elements:
For any issues found, facilitate resolution:
**Critical Issues:**
"I found some issues that need to be addressed before implementation:
<display>
I found some issues that need to be addressed before implementation:
{{critical_issue_description}}
These could cause implementation problems. How would you like to resolve this?"
These could cause implementation problems. How would you like to resolve this?
</display>
**Important Issues:**
"I noticed a few areas that could be improved:
<display>
I noticed a few areas that could be improved:
{{important_issue_description}}
These aren't blocking, but addressing them would make implementation smoother. Should we work on these?"
These aren't blocking, but addressing them would make implementation smoother. Should we work on these?
</display>
**Minor Issues:**
"Here are some minor suggestions for improvement:
<display>
Here are some minor suggestions for improvement:
{{minor_issue_description}}
These are optional refinements. Would you like to address any of these?"
These are optional refinements. Would you like to address any of these?
</display>
### 6. Generate Validation Content
@ -284,7 +290,8 @@ Prepare the content to append to the document:
Show the validation results and present choices:
"I've completed a comprehensive validation of your architecture.
<display>
I've completed a comprehensive validation of your architecture.
**Validation Summary:**
@ -300,6 +307,7 @@ Show the validation results and present choices:
[A] Advanced Elicitation - Address any complex architectural concerns
[P] Party Mode - Review validation from different implementation perspectives
[C] Continue - Complete the architecture and finish workflow
</display>
### 8. Handle Menu Selection

10
src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md
View File

@ -67,7 +67,9 @@ a) **Menu Handling:**
a) **Greet the user briefly:**
"Hey {user_name}! What are we building today?"
<display>
Hey {user_name}! What are we building today?
</display>
b) **Get their initial description.** Don't ask detailed questions yet - just understand enough to know where to look.
@ -150,13 +152,15 @@ a) **Create the tech-spec WIP file:**
b) **Report to user:**
"Created: `{wipFile}`
<display>
Created: `{wipFile}`
**Captured:**
- Title: {title}
- Problem: {problem_statement_summary}
- Scope: {scope_summary}"
- Scope: {scope_summary}
</display>
### 6. Present Checkpoint Menu

10
src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md
View File

@ -45,7 +45,9 @@ a) **Build on Step 1's Quick Scan**
Review what was found in Step 1's orient scan. Then ask:
"Based on my quick look, I see [files/patterns found]. Are there other files or directories I should investigate deeply?"
<display>
Based on my quick look, I see [files/patterns found]. Are there other files or directories I should investigate deeply?
</display>
b) **Read and Analyze Code**
@ -106,12 +108,14 @@ Fill in:
**Report to user:**
"**Context Gathered:**
<display>
**Context Gathered:**
- Tech Stack: {tech_stack_summary}
- Files to Modify: {files_count} files identified
- Patterns: {patterns_summary}
- Tests: {test_patterns_summary}"
- Tests: {test_patterns_summary}
</display>
### 4. Present Checkpoint Menu

12
src/bmm/workflows/document-project/instructions.md
View File

@ -94,7 +94,7 @@ Your choice [1/2/3]:
<action>Skip loading project-types.csv and architecture_registry.csv (not needed on resume)</action>
<action>Store loaded doc requirements for use in remaining steps</action>
<action>Display: "Resuming {{workflow_mode}} from {{current_step}} with cached project type(s): {{cached_project_types}}"</action>
<display>Resuming {{workflow_mode}} from {{current_step}} with cached project type(s): {{cached_project_types}}</display>
<check if="workflow_mode == deep_dive">
<action>Read fully and follow: {installed_path}/workflows/deep-dive-instructions.md with resume context</action>
@ -114,12 +114,12 @@ Your choice [1/2/3]:
</check>
<check if="user selects 3">
<action>Display: "Exiting workflow without changes."</action>
<display>Exiting workflow without changes.</display>
<action>Exit workflow</action>
</check>
<check if="state file age >= 24 hours">
<action>Display: "Found old state file (>24 hours). Starting fresh scan."</action>
<display>Found old state file (>24 hours). Starting fresh scan.</display>
<action>Archive old state file to: {output_folder}/.archive/project-scan-report-{{timestamp}}.json</action>
<action>Set resume_mode = false</action>
<action>Continue to Step 0.5</action>
@ -147,7 +147,7 @@ Your choice [1/2/3]:
<check if="user selects 1">
<action>Set workflow_mode = "full_rescan"</action>
<action>Display: "Starting full project rescan..."</action>
<display>Starting full project rescan...</display>
<action>Read fully and follow: {installed_path}/workflows/full-scan-instructions.md</action>
<action>After sub-workflow completes, continue to Step 4</action>
</check>
@ -155,7 +155,7 @@ Your choice [1/2/3]:
<check if="user selects 2">
<action>Set workflow_mode = "deep_dive"</action>
<action>Set scan_level = "exhaustive"</action>
<action>Display: "Starting deep-dive documentation mode..."</action>
<display>Starting deep-dive documentation mode...</display>
<action>Read fully and follow: {installed_path}/workflows/deep-dive-instructions.md</action>
<action>After sub-workflow completes, continue to Step 4</action>
</check>
@ -168,7 +168,7 @@ Your choice [1/2/3]:
<check if="index.md does not exist">
<action>Set workflow_mode = "initial_scan"</action>
<action>Display: "No existing documentation found. Starting initial project scan..."</action>
<display>No existing documentation found. Starting initial project scan...</display>
<action>Read fully and follow: {installed_path}/workflows/full-scan-instructions.md</action>
<action>After sub-workflow completes, continue to Step 4</action>
</check>

30
src/bmm/workflows/document-project/workflows/full-scan-instructions.md
View File

@ -37,9 +37,9 @@ This workflow uses a single comprehensive CSV file to intelligently document you
<action>Load documentation-requirements.csv from: {documentation_requirements_csv}</action>
<action>Store all 12 rows indexed by project_type_id for project detection and requirements lookup</action>
<action>Display: "Loaded documentation requirements for 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)"</action>
<display>Loaded documentation requirements for 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)</display>
<action>Display: "✓ Documentation requirements loaded successfully. Ready to begin project analysis."</action>
<display>✓ Documentation requirements loaded successfully. Ready to begin project analysis.</display>
</step>
<step n="0.6" goal="Check for existing documentation and determine workflow mode">
@ -114,17 +114,17 @@ Your choice [1/2/3] (default: 1):
<action if="user selects 1 OR user presses enter">
<action>Set scan_level = "quick"</action>
<action>Display: "Using Quick Scan (pattern-based, no source file reading)"</action>
<display>Using Quick Scan (pattern-based, no source file reading)</display>
</action>
<action if="user selects 2">
<action>Set scan_level = "deep"</action>
<action>Display: "Using Deep Scan (reading critical files per project type)"</action>
<display>Using Deep Scan (reading critical files per project type)</display>
</action>
<action if="user selects 3">
<action>Set scan_level = "exhaustive"</action>
<action>Display: "Using Exhaustive Scan (reading all source files)"</action>
<display>Using Exhaustive Scan (reading all source files)</display>
</action>
<action>Initialize state file: {output_folder}/project-scan-report.json</action>
@ -915,7 +915,7 @@ Enter number(s) separated by commas (e.g., "1,3,5"), or type 'all':
- Store result in {{selected_items}} array
</action>
<action>Display: "Generating {{selected_items.length}} document(s)..."</action>
<display>Generating {{selected_items.length}} document(s)...</display>
<action>For each item in {{selected_items}}:
@ -927,7 +927,7 @@ Enter number(s) separated by commas (e.g., "1,3,5"), or type 'all':
2. **Route to appropriate generation substep based on doc_type:**
**If doc_type == "architecture":**
- Display: "Generating architecture documentation for {{part_id}}..."
- <display>Generating architecture documentation for {{part_id}}...</display>
- Load architecture_match for this part from state file (Step 3 cache)
- Re-run Step 8 architecture generation logic ONLY for this specific part
- Use matched template and fill with cached data from state file
@ -935,7 +935,7 @@ Enter number(s) separated by commas (e.g., "1,3,5"), or type 'all':
- Validate completeness
**If doc_type == "api-contracts":**
- Display: "Generating API contracts for {{part_id}}..."
- <display>Generating API contracts for {{part_id}}...</display>
- Load part data and documentation_requirements
- Re-run Step 4 API scan substep targeting ONLY this part
- Use scan_level from state file (quick/deep/exhaustive)
@ -943,35 +943,35 @@ Enter number(s) separated by commas (e.g., "1,3,5"), or type 'all':
- Validate document structure
**If doc_type == "data-models":**
- Display: "Generating data models documentation for {{part_id}}..."
- <display>Generating data models documentation for {{part_id}}...</display>
- Re-run Step 4 data models scan substep targeting ONLY this part
- Use schema_migration_patterns from documentation_requirements
- Generate data-models-{{part_id}}.md
- Validate completeness
**If doc_type == "component-inventory":**
- Display: "Generating component inventory for {{part_id}}..."
- <display>Generating component inventory for {{part_id}}...</display>
- Re-run Step 9 component inventory generation for this specific part
- Scan components/, ui/, widgets/ folders
- Generate component-inventory-{{part_id}}.md
- Validate structure
**If doc_type == "development-guide":**
- Display: "Generating development guide for {{part_id}}..."
- <display>Generating development guide for {{part_id}}...</display>
- Re-run Step 9 development guide generation for this specific part
- Use key_file_patterns and test_file_patterns from documentation_requirements
- Generate development-guide-{{part_id}}.md
- Validate completeness
**If doc_type == "deployment-guide":**
- Display: "Generating deployment guide..."
- <display>Generating deployment guide...</display>
- Re-run Step 6 deployment configuration scan
- Re-run Step 9 deployment guide generation
- Generate deployment-guide.md
- Validate structure
**If doc_type == "integration-architecture":**
- Display: "Generating integration architecture..."
- <display>Generating integration architecture...</display>
- Re-run Step 7 integration analysis for all parts
- Generate integration-architecture.md
- Validate completeness
@ -980,7 +980,7 @@ Enter number(s) separated by commas (e.g., "1,3,5"), or type 'all':
- Confirm file was written successfully
- Update state file with newly generated output
- Add to {{newly_generated_docs}} tracking list
- Display: "✓ Generated: {{file_path}}"
- <display>✓ Generated: {{file_path}}</display>
4. **Handle errors:**
- If generation fails, log error and continue with next item
@ -1101,6 +1101,6 @@ When ready to plan new features, run the PRD workflow and provide this index as
- Write final state file
</action>
<action>Display: "State file saved: {{output_folder}}/project-scan-report.json"</action>
<display>State file saved: {{output_folder}}/project-scan-report.json</display>
</workflow>

6
src/bmm/workflows/generate-project-context/steps/step-01-discover.md
View File

@ -135,7 +135,8 @@ Set frontmatter `sections_completed` to track what will be updated
Report findings to user:
"Welcome {{user_name}}! I've analyzed your project for {{project_name}} to discover the context that AI agents need.
<display>
Welcome {{user_name}}! I've analyzed your project for {{project_name}} to discover the context that AI agents need.
**Technology Stack Discovered:**
{{list_of_technologies_with_versions}}
@ -158,7 +159,8 @@ Report findings to user:
Ready to create/update your project context. This will help AI agents implement code consistently with your project's standards.
[C] Continue to context generation"
[C] Continue to context generation
</display>
## SUCCESS METRICS:

60
src/bmm/workflows/generate-project-context/steps/step-02-generate.md
View File

@ -55,13 +55,16 @@ Document the exact technology stack from discovery:
Based on user skill level, present findings:
**Expert Mode:**
"Technology stack from your architecture and package files:
<display>
Technology stack from your architecture and package files:
{{exact_technologies_with_versions}}
Any critical version constraints I should document for agents?"
Any critical version constraints I should document for agents?
</display>
**Intermediate Mode:**
"I found your technology stack:
<display>
I found your technology stack:
**Core Technologies:**
{{main_technologies_with_versions}}
@ -69,10 +72,12 @@ Any critical version constraints I should document for agents?"
**Key Dependencies:**
{{important_dependencies_with_versions}}
Are there any version constraints or compatibility notes agents should know about?"
Are there any version constraints or compatibility notes agents should know about?
</display>
**Beginner Mode:**
"Here are the technologies you're using:
<display>
Here are the technologies you're using:
**Main Technologies:**
{{friendly_description_of_tech_stack}}
@ -80,14 +85,16 @@ Are there any version constraints or compatibility notes agents should know abou
**Important Notes:**
{{key_things_agents_need_to_know_about_versions}}
Should I document any special version rules or compatibility requirements?"
Should I document any special version rules or compatibility requirements?
</display>
### 2. Language-Specific Rules
Focus on unobvious language patterns agents might miss:
**TypeScript/JavaScript Rules:**
"Based on your codebase, I notice some specific patterns:
<display>
Based on your codebase, I notice some specific patterns:
**Configuration Requirements:**
{{typescript_config_rules}}
@ -98,7 +105,8 @@ Focus on unobvious language patterns agents might miss:
**Error Handling Patterns:**
{{error_handling_requirements}}
Are these patterns correct? Any other language-specific rules agents should follow?"
Are these patterns correct? Any other language-specific rules agents should follow?
</display>
**Python/Ruby/Other Language Rules:**
Adapt to the actual language in use with similar focused questions.
@ -108,7 +116,8 @@ Adapt to the actual language in use with similar focused questions.
Document framework-specific patterns:
**React Rules (if applicable):**
"For React development, I see these patterns:
<display>
For React development, I see these patterns:
**Hooks Usage:**
{{hooks_usage_patterns}}
@ -122,7 +131,8 @@ Document framework-specific patterns:
**Performance Rules:**
{{performance_optimization_requirements}}
Should I add any other React-specific rules?"
Should I add any other React-specific rules?
</display>
**Other Framework Rules:**
Adapt for Vue, Angular, Next.js, Express, etc.
@ -132,7 +142,8 @@ Adapt for Vue, Angular, Next.js, Express, etc.
Focus on testing patterns that ensure consistency:
**Test Structure Rules:**
"Your testing setup shows these patterns:
<display>
Your testing setup shows these patterns:
**Test Organization:**
{{test_file_organization}}
@ -146,14 +157,16 @@ Focus on testing patterns that ensure consistency:
**Integration vs Unit Test Rules:**
{{test_boundary_patterns}}
Are there testing rules agents should always follow?"
Are there testing rules agents should always follow?
</display>
### 5. Code Quality & Style Rules
Document critical style and quality rules:
**Linting/Formatting:**
"Your code style configuration requires:
<display>
Your code style configuration requires:
**ESLint/Prettier Rules:**
{{specific_linting_rules}}
@ -167,14 +180,16 @@ Document critical style and quality rules:
**Documentation Requirements:**
{{comment_and_documentation_patterns}}
Any additional code quality rules?"
Any additional code quality rules?
</display>
### 6. Development Workflow Rules
Document workflow patterns that affect implementation:
**Git/Repository Rules:**
"Your project uses these patterns:
<display>
Your project uses these patterns:
**Branch Naming:**
{{branch_naming_conventions}}
@ -188,14 +203,16 @@ Document workflow patterns that affect implementation:
**Deployment Patterns:**
{{deployment_considerations}}
Should I document any other workflow rules?"
Should I document any other workflow rules?
</display>
### 7. Critical Don't-Miss Rules
Identify rules that prevent common mistakes:
**Anti-Patterns to Avoid:**
"Based on your codebase, here are critical things agents must NOT do:
<display>
Based on your codebase, here are critical things agents must NOT do:
{{critical_anti_patterns_with_examples}}
@ -208,7 +225,8 @@ Identify rules that prevent common mistakes:
**Performance Gotchas:**
{{performance_patterns_to_avoid}}
Are there other 'gotchas' agents should know about?"
Are there other 'gotchas' agents should know about?
</display>
### 8. Generate Context Content
@ -252,7 +270,8 @@ For each category, prepare lean content for the project context file:
After each category, show the generated rules and present choices:
"I've drafted the {{category_name}} rules for your project context.
<display>
I've drafted the {{category_name}} rules for your project context.
**Here's what I'll add:**
@ -261,7 +280,8 @@ After each category, show the generated rules and present choices:
**What would you like to do?**
[A] Advanced Elicitation - Explore nuanced rules for this category
[P] Party Mode - Review from different implementation perspectives
[C] Continue - Save these rules and move to next category"
[C] Continue - Save these rules and move to next category
</display>
### 10. Handle Menu Selection

30
src/bmm/workflows/generate-project-context/steps/step-03-complete.md
View File

@ -133,14 +133,17 @@ Last Updated: {{date}}
Based on user skill level, present the completion:
**Expert Mode:**
"Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections.
<display>
Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections.
File saved to: `{output_folder}/project-context.md`
Ready for AI agent integration."
Ready for AI agent integration.
</display>
**Intermediate Mode:**
"Your project context is complete and optimized for AI agents!
<display>
Your project context is complete and optimized for AI agents!
**What we created:**
@ -160,10 +163,12 @@ Ready for AI agent integration."
- AI agents should read this file before implementing
- Update as your project evolves
- Review periodically for optimization"
- Review periodically for optimization
</display>
**Beginner Mode:**
"Excellent! Your project context guide is ready! 🎉
<display>
Excellent! Your project context guide is ready!
**What this does:**
Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
@ -178,7 +183,8 @@ Think of this as a 'rules of the road' guide for AI agents working on your proje
**How AI agents use it:**
They read this file before writing any code, ensuring everything they create follows your project's standards perfectly.
Your project context is saved and ready to help agents implement consistently!"
Your project context is saved and ready to help agents implement consistently!
</display>
### 5. Final File Updates
@ -225,32 +231,34 @@ Final checks before completion:
Present final completion to user:
"✅ **Project Context Generation Complete!**
<display>
**Project Context Generation Complete!**
Your optimized project context file is ready at:
`{output_folder}/project-context.md`
**📊 Context Summary:**
**Context Summary:**
- {{rule_count}} critical rules for AI agents
- {{section_count}} comprehensive sections
- Optimized for LLM context efficiency
- Ready for immediate agent integration
**🎯 Key Benefits:**
**Key Benefits:**
- Consistent implementation across all AI agents
- Reduced common mistakes and edge cases
- Clear guidance for project-specific patterns
- Minimal LLM context usage
**📋 Next Steps:**
**Next Steps:**
1. AI agents will automatically read this file when implementing
2. Update this file when your technology stack or patterns evolve
3. Review quarterly to optimize and remove outdated rules
Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!"
Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!
</display>
## SUCCESS METRICS:

18
src/core/workflows/brainstorming/steps/step-03-technique-execution.md
View File

@ -140,11 +140,13 @@ Great starting point! Sometimes the most powerful ideas need space to develop. L
</display>
**When user gives detailed response:**
"Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
<display>
Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
**Key Insight:** [Extract and highlight their best point]
**Building on That:** [Develop their idea further]
**Additional Direction:** [Suggest new angles based on their thinking]"
**Additional Direction:** [Suggest new angles based on their thinking]
</display>
### 4. Check Technique Continuation
@ -177,7 +179,8 @@ This has been incredibly productive! We've generated some fantastic ideas around
**Periodic Check-In (DO NOT skip this):**
"We've generated [X] ideas so far - great momentum!
<display>
We've generated [X] ideas so far - great momentum!
**Quick energy check:**
@ -185,7 +188,8 @@ This has been incredibly productive! We've generated some fantastic ideas around
- **Switch techniques** for a fresh perspective?
- Or are you feeling like we've **thoroughly explored** this space?
Remember: The goal is quantity first - we can organize later. What feels right?"
Remember: The goal is quantity first - we can organize later. What feels right?
</display>
**IMPORTANT:** Default to continuing exploration. Only suggest organization if:
@ -256,11 +260,13 @@ Capture insights as they emerge during interactive facilitation:
**During Facilitation:**
"That's a powerful insight - let me capture that: _[Key idea with context]_
<display>
That's a powerful insight - let me capture that: _[Key idea with context]_
I'm noticing a theme emerging here: _[Pattern recognition]_
This connects beautifully with what we discovered earlier about _[previous connection]_"
This connects beautifully with what we discovered earlier about _[previous connection]_
</display>
**After Deep Exploration:**

10
src/core/workflows/party-mode/steps/step-03-graceful-exit.md
View File

@ -70,7 +70,9 @@ For each selected agent:
Briefly acknowledge key discussion outcomes:
**Session Recognition:**
"**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint."
<display>
**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint.
</display>
### 4. Final Party Mode Conclusion
@ -116,9 +118,11 @@ workflow_completed: true
Execute final workflow termination:
"[PARTY MODE WORKFLOW COMPLETE]
<display>
[PARTY MODE WORKFLOW COMPLETE]
Thank you for using BMAD Party Mode for collaborative multi-agent discussions!"
Thank you for using BMAD Party Mode for collaborative multi-agent discussions!
</display>
## SUCCESS METRICS: