convoke-agents 2.0.0

package/_bmad/bme/_vortex/workflows/_deprecated/empathy-map/steps/step-05-gains.md

@@ -0,0 +1,103 @@
+---
+step: 5
+workflow: empathy-map
+title: Gains
+---
+
+# Step 5: Gains
+
+Let's identify what your target user **wants to achieve** - their desired outcomes, needs, and measures of success.
+
+## Why This Matters
+
+Pain points show us problems. Gains show us aspirations. Together they give us a complete picture:
+- Pain points → What to fix
+- Gains → What to enable
+
+Understanding gains helps us:
+- Design solutions that deliver meaningful value
+- Prioritize features based on desired outcomes
+- Measure success from the user's perspective
+
+## Types of Gains
+
+**Functional Gains** - Tasks completed faster, processes simplified, efficiency improved
+
+**Emotional Gains** - Reduced stress, increased confidence, peace of mind
+
+**Social Gains** - Better collaboration, improved reputation, team alignment
+
+**Aspirational Gains** - Career advancement, skill development, professional growth
+
+## Your Task
+
+### Identify 4-6 Gains
+
+For each gain, capture:
+1. **The Gain** - What do they want to achieve?
+2. **The Value** - Why does this matter to them?
+3. **Success Metric** - How would they know they achieved it?
+
+**Example:**
+
+**Gain #1: See All Campaign Performance in One Dashboard**
+- **Value:** Stop wasting time switching tools; make faster data-driven decisions
+- **Success Metric:** Can check all campaign metrics in under 2 minutes vs. current 15 minutes
+
+**Gain #2: Automated Lead Scoring**
+- **Value:** Send higher-quality leads to sales, improving marketing-sales relationship and conversion rates
+- **Success Metric:** Sales team accepts 80%+ of marketing-qualified leads vs. current 45%
+
+**Gain #3: Predict Campaign Performance Early**
+- **Value:** Optimize underperforming campaigns before budget is wasted; increase ROI
+- **Success Metric:** Adjust campaigns within first 48 hours based on performance signals
+
+**Gain #4: Collaborative Campaign Planning**
+- **Value:** Get team alignment before launch instead of fixing issues after launch
+- **Success Metric:** Team approves campaign plan in 1 meeting vs. current 3-4 rounds of revisions
+
+## Tips for Success
+
+**Link to Pain Points:**
+- Gains often flip pain points into aspirations
+- Pain: "Data scattered across 6 tools" → Gain: "See everything in one dashboard"
+
+**Be Outcome-Focused:**
+- Not "Use our tool" but "Complete campaigns 30% faster"
+- Not "Have more features" but "Reduce manual work by 50%"
+
+**Include Metrics:**
+- Time saved
+- Quality improved
+- Confidence increased
+- Collaboration enhanced
+
+**Distinguish Must-Haves from Nice-to-Haves:**
+- Which gains are critical for user success?
+- Which gains are differentiators vs. table stakes?
+
+## Connecting Gains to Pain Points
+
+Notice how gains address pain points:
+
+| Pain Point | Desired Gain |
+|------------|--------------|
+| Data scattered across 6 tools | Unified dashboard with all metrics |
+| Can't see real-time performance | Live campaign analytics with alerts |
+| Manual lead scoring | Automated lead qualification |
+| Time-consuming report generation | One-click reports with key insights |
+
+---
+
+## Your Turn
+
+Please identify 4-6 gains your target user desires. For each gain, include:
+1. What they want to achieve
+2. Why it matters (the value)
+3. How they'd measure success
+
+## Next Step
+
+When you've documented the desired gains, I'll load:
+
+{project-root}/_bmad/bme/_designos/workflows/empathy-map/steps/step-06-synthesize.md

package/_bmad/bme/_vortex/workflows/_deprecated/empathy-map/steps/step-06-synthesize.md

@@ -0,0 +1,104 @@
+---
+step: 6
+workflow: empathy-map
+title: Synthesize
+---
+
+# Step 6: Synthesize
+
+Time to bring it all together and create the final empathy map artifact.
+
+## Why This Matters
+
+We've gathered rich insights across 5 dimensions (Says, Thinks, Does, Feels, Pains, Gains). Now we need to synthesize them into a coherent, actionable empathy map that:
+- Tells a compelling story about the user
+- Reveals patterns and insights
+- Guides design and product decisions
+
+## Your Task
+
+### 1. Review All Insights
+
+Look across all the data you've captured:
+- Target user definition (Step 1)
+- Says & Thinks (Step 2)
+- Does & Feels (Step 3)
+- Pain Points (Step 4)
+- Gains (Step 5)
+
+### 2. Identify Key Insights
+
+What patterns emerge? What surprises you? What's most important?
+
+**Example Insights:**
+- "Sarah says she wants more features, but really needs simplification - her current process involves 6 tools"
+- "Biggest pain isn't the tool itself, it's the data silos preventing real-time decisions"
+- "Anxiety about missing notifications drives obsessive email checking - automation would reduce stress"
+
+### 3. Create the Empathy Map
+
+I'll use the template at `empathy-map.template.md` to generate your final artifact.
+
+**Output File:** `{output_folder}/empathy-map-{user-name}-{date}.md`
+
+### 4. Validation Questions
+
+Before we finalize, let's validate:
+
+**Evidence Check:**
+- [ ] Is every insight backed by research (quotes, observations, data)?
+- [ ] Did we avoid speculation and assumptions?
+- [ ] Can we trace each insight back to a specific source?
+
+**Specificity Check:**
+- [ ] Is the target user definition specific enough?
+- [ ] Are pain points concrete and actionable?
+- [ ] Are gains measurable?
+
+**Actionability Check:**
+- [ ] Can designers use this to inform wireframes?
+- [ ] Can product managers use this to prioritize features?
+- [ ] Can developers use this to understand user context?
+
+**Completeness Check:**
+- [ ] Did we capture both positive and negative aspects?
+- [ ] Did we explore emotions, not just behaviors?
+- [ ] Did we understand the WHY, not just the WHAT?
+
+---
+
+## Your Turn
+
+Please review all your insights and identify 3-5 key patterns or surprises that emerged.
+
+Then confirm you're ready for me to generate the final empathy map artifact.
+
+## Output
+
+Once you confirm, I'll create:
+
+**File:** `{output_folder}/empathy-map-{user-name}-{date}.md`
+
+**Contents:**
+- Executive Summary (key insights)
+- Target User Profile
+- Says & Thinks
+- Does & Feels
+- Pain Points (prioritized)
+- Desired Gains (prioritized)
+- Design Implications
+- Research Sources
+
+---
+
+## What's Next?
+
+After creating this empathy map, you might:
+
+1. **Validate with users** - Show the empathy map to actual users and ask if it resonates
+2. **Share with team** - Get stakeholder alignment on user needs
+3. **Create wireframes** - Use insights to inform design decisions (invoke Wade!)
+4. **Prioritize features** - Focus on gains that address the biggest pain points
+5. **Define success metrics** - Use gain metrics to track if solutions work
+
+Great work! This empathy map will be a valuable tool for user-centered decision making. 🎨

package/_bmad/bme/_vortex/workflows/_deprecated/empathy-map/validate.md

@@ -0,0 +1,117 @@
+---
+workflow: validate-empathy-map
+type: single-file
+description: Validate an existing empathy map against user research evidence
+author: Emma (contextualization-expert)
+---
+
+# Validate Existing Empathy Map
+
+Bring me an empathy map and I'll help you validate it against user research evidence.
+
+## Why Validation Matters
+
+Empathy maps lose value if they're based on assumptions instead of research. Validation ensures:
+- Every insight traces back to evidence
+- No speculation or "we think users want..."
+- Team stays grounded in user reality
+
+## Validation Process
+
+### 1. Evidence Check
+
+For each insight in the empathy map, ask:
+
+**Can you point to research that supports this?**
+- Direct quote from interview?
+- Observed behavior?
+- Survey data?
+- Analytics?
+
+**Red Flags:**
+- "We think users want..."
+- "Users probably feel..."
+- "Based on our internal discussions..."
+- No citation to research source
+
+### 2. Specificity Check
+
+**Is the target user specific enough?**
+- ❌ "Mobile users"
+- ❌ "Marketing professionals"
+- ✅ "Marketing managers at mid-sized B2B companies managing lead generation"
+
+**Are pain points concrete?**
+- ❌ "Bad UX"
+- ✅ "Campaign creation button hidden in nested menu (3 clicks deep)"
+
+**Are gains measurable?**
+- ❌ "Want to be more efficient"
+- ✅ "Complete campaign setup in under 10 minutes vs. current 45 minutes"
+
+### 3. Completeness Check
+
+**Did you explore all dimensions?**
+- [ ] Says (direct quotes)
+- [ ] Thinks (inferred thoughts)
+- [ ] Does (observable actions)
+- [ ] Feels (emotional states)
+- [ ] Pains (obstacles/frustrations)
+- [ ] Gains (desired outcomes)
+
+**Did you capture both positive and negative?**
+- Not just problems (pain points)
+- Also aspirations (gains)
+- Moments of delight AND frustration
+
+### 4. Actionability Check
+
+**Can designers use this?**
+- Are pain points specific enough to inform design decisions?
+- Are gains clear enough to prioritize features?
+
+**Can product managers use this?**
+- Can they defend feature decisions with user insights?
+- Can they communicate user needs to stakeholders?
+
+---
+
+## Your Turn
+
+**Please share:**
+1. The empathy map you want to validate (paste content or provide file path)
+2. The research sources that informed it
+
+I'll review it and provide:
+- **Evidence gaps** - Insights lacking research support
+- **Specificity issues** - Vague statements that need clarification
+- **Missing dimensions** - Areas you didn't explore
+- **Validation score** - Overall assessment (Strong / Needs Work / Speculative)
+
+---
+
+## Validation Criteria
+
+**Strong Empathy Map:**
+- ✅ Every insight backed by cited research
+- ✅ Specific target user definition
+- ✅ Concrete, measurable pain points and gains
+- ✅ All 6 dimensions explored (Says, Thinks, Does, Feels, Pains, Gains)
+- ✅ Both positive and negative aspects captured
+- ✅ Actionable for designers and product managers
+
+**Needs Work:**
+- ⚠️ Some insights lack research support
+- ⚠️ Target user could be more specific
+- ⚠️ Pain points or gains are vague
+- ⚠️ Missing some dimensions
+
+**Speculative:**
+- ❌ Many insights are assumptions
+- ❌ No clear research sources
+- ❌ "We think" instead of "Users said"
+- ❌ Not actionable
+
+---
+
+Ready to validate your empathy map? Share it with me and I'll provide detailed feedback! 🎨

package/_bmad/bme/_vortex/workflows/_deprecated/empathy-map/workflow.md

@@ -0,0 +1,44 @@
+---
+workflow: empathy-map
+type: step-file
+description: Create user empathy maps through structured 6-step process
+author: Emma (contextualization-expert)
+---
+
+# Create Empathy Map Workflow
+
+This workflow guides you through creating a comprehensive empathy map for a target user.
+
+## What is an Empathy Map?
+
+An empathy map is a collaborative visualization used to articulate what we know about a particular type of user. It externalizes knowledge about users to create a shared understanding and aid decision-making.
+
+## Workflow Structure
+
+**Step-file architecture:**
+- Just-in-time loading (each step loads only when needed)
+- Sequential enforcement (must complete step N before step N+1)
+- State tracking in frontmatter (progress preserved)
+
+## Steps Overview
+
+1. **Define Target User** - Who are we creating this empathy map for?
+2. **Says & Thinks** - What do they say aloud? What do they think?
+3. **Does & Feels** - What actions do they take? What emotions do they feel?
+4. **Pain Points** - What frustrates, blocks, or challenges them?
+5. **Gains** - What do they want to achieve? What are their needs?
+6. **Synthesize** - Create the final empathy map artifact
+
+## Output
+
+**Artifact:** Empathy map markdown file in `{output_folder}/empathy-map-{user-name}-{date}.md`
+
+**Template:** Uses [empathy-map.template.md](empathy-map.template.md)
+
+---
+
+## INITIALIZATION
+
+Load config from {project-root}/_bmad/bme/_designos/config.yaml
+
+Load step: {project-root}/_bmad/bme/_designos/workflows/empathy-map/steps/step-01-define-user.md

package/_bmad/bme/_vortex/workflows/_deprecated/wireframe/steps/step-01-define-requirements.md

@@ -0,0 +1,85 @@
+---
+step: 1
+workflow: wireframe
+title: Define Requirements
+---
+
+# Step 1: Define Requirements
+
+Before we create a wireframe, we need to understand exactly what we're building and why.
+
+## Why This Matters
+
+A wireframe is only useful if it solves a real problem. Generic wireframes waste time. Specific wireframes (for a specific screen, user, and goal) accelerate design and development.
+
+## Your Task
+
+Answer these questions to define your wireframe requirements:
+
+### 1. What are we wireframing?
+
+- **Scope:** Single screen? User flow (multiple screens)? Full app?
+- **Screen name:** What do you call this screen? (e.g., "Dashboard Home", "Checkout Flow", "Product Detail Page")
+- **Platform:** Web (desktop)? Web (mobile)? Mobile app (iOS/Android)?
+- **Viewport size:**
+  - Mobile: 375px width (iPhone standard)
+  - Tablet: 768px width
+  - Desktop: 1024px+ width
+  - Responsive: All of the above?
+
+### 2. Who is this for?
+
+- **Target user:** Who will use this screen? (Reference an empathy map if available, e.g., "Sarah Chen from empathy-map-sarah-chen-2026-02-14.md")
+- **User's primary goal:** What is the ONE thing users come here to do?
+- **User's technical proficiency:** Tech-savvy? Average? Non-technical?
+- **User context:** Are they rushed? Exploring? Completing a specific task?
+
+### 3. What's the core functionality?
+
+- **Primary action:** The MAIN thing users do on this screen (e.g., "Check account balance")
+- **Secondary actions:** Supporting tasks (e.g., "View recent transactions", "Transfer money")
+- **Information displayed:** What data does the screen show? (e.g., "Balance, last 5 transactions, quick action buttons")
+- **Data sources:** Where does the information come from? (APIs, databases, user input)
+
+### 4. Design constraints?
+
+- **Existing design system?** Are you using Material Design, iOS Human Interface Guidelines, custom component library?
+- **Brand guidelines?** Any must-have elements (logo placement, color scheme - high level only)
+- **Technical constraints?** Third-party integrations, API limitations, performance requirements?
+- **Accessibility requirements?** WCAG 2.1 Level AA compliance? Screen reader support?
+
+## Example
+
+```
+Screen: Dashboard Home (Mobile Banking App)
+Platform: Mobile app (iOS/Android)
+Viewport: 375px width (mobile-first)
+
+User: Sarah Chen (see empathy-map-sarah-chen-2026-02-14.md)
+Primary Goal: Check account balance quickly
+Technical Proficiency: Medium-high
+Context: Rushed, 3-5 daily check-ins, sessions < 2 minutes
+
+Primary Action: Check account balance
+Secondary Actions: View recent transactions, quick transfer, pay bills
+Information: Balance, last updated timestamp, 5 recent transactions, quick action buttons
+Data Sources: Banking API (balance, transactions)
+
+Constraints:
+- Must support Face ID for authentication
+- Follow iOS/Android platform patterns
+- WCAG 2.1 Level AA (minimum 44px touch targets)
+- Performance: Load balance in < 1 second
+```
+
+---
+
+## Your Turn
+
+Please define your wireframe requirements using the structure above.
+
+## Next Step
+
+When you've defined your requirements and I've confirmed they're specific enough, I'll load:
+
+{project-root}/_bmad/bme/_designos/workflows/wireframe/steps/step-02-user-flows.md

package/_bmad/bme/_vortex/workflows/_deprecated/wireframe/steps/step-02-user-flows.md

@@ -0,0 +1,59 @@
+---
+step: 2
+workflow: wireframe
+title: User Flows
+---
+
+# Step 2: User Flows
+
+Let's map how users navigate through your wireframe(s).
+
+## Why This Matters
+
+Understanding user flows prevents designing dead-end screens or confusing navigation. Every screen needs clear entry points and exit points.
+
+## Your Task
+
+### 1. Entry Points
+How do users arrive at this screen?
+- From home screen? From search? From notification?
+- Deep link? QR code? Email link?
+- What's their mental state? (rushing, exploring, completing task)
+
+### 2. Primary Flow (Happy Path)
+Map the ideal journey from entry to goal completion:
+
+```
+Entry → Action → Response → Goal Achieved
+```
+
+Example:
+```
+Home Screen
+    ↓ (Tap "Balance")
+Face ID Authentication
+    ↓ (Success)
+Balance Display
+    ↓ (Goal: See balance)
+[Done] or Continue to Secondary Action
+```
+
+### 3. Alternative Flows
+What if...?
+- User makes an error?
+- Data is unavailable?
+- Authentication fails?
+- User wants to go back?
+- User abandons the flow?
+
+### 4. Exit Points
+How do users leave?
+- Goal completed → where next?
+- Task abandoned → how to recover?
+- Navigation to related features?
+
+## Next Step
+
+When you've mapped user flows, I'll load:
+
+{project-root}/_bmad/bme/_designos/workflows/wireframe/steps/step-03-information-architecture.md

package/_bmad/bme/_vortex/workflows/_deprecated/wireframe/steps/step-03-information-architecture.md

@@ -0,0 +1,68 @@
+---
+step: 3
+workflow: wireframe
+title: Information Architecture
+---
+
+# Step 3: Information Architecture
+
+Let's organize content and UI elements hierarchically.
+
+## Your Task
+
+### 1. Content Priority (Visual Hierarchy)
+What's most important on this screen?
+
+**Primary (above the fold, largest/boldest):**
+- The ONE thing users came here to see/do
+
+**Secondary (mid-screen, medium emphasis):**
+- Supporting information and actions
+
+**Tertiary (below fold or subtle):**
+- Metadata, help text, less critical features
+
+### 2. Grouping
+How to organize related elements?
+
+- **Visual grouping:** Cards? Sections? Accordions?
+- **Logical grouping:** By task? By time? By category?
+- **Separation:** Spacing? Dividers? Background colors?
+
+### 3. Navigation
+How do users move around?
+
+- **Primary nav:** Top bar? Bottom tabs? Sidebar? Hamburger menu?
+- **Secondary nav:** Breadcrumbs? Tabs? Segmented controls?
+- **Back/Close:** Where do these buttons go?
+
+### 4. Information Density
+How much is too much?
+
+- **Progressive disclosure:** Show essentials, hide details until needed
+- **Lazy loading:** Load more on scroll?
+- **Pagination vs. infinite scroll**
+
+## Example
+
+```
+Dashboard Screen (Mobile - 375px)
+
+[Visual Hierarchy]
+Primary: Account balance ($$$) - Hero section, centered, large
+Secondary: Quick actions (3 buttons) - Mid section
+Tertiary: Recent transactions (list) - Bottom, scrollable
+
+[Grouping]
+Section 1: Hero (balance + last updated)
+Section 2: Quick Actions (3 icon buttons, horizontal)
+Section 3: Activity (transaction list with "Load More")
+
+[Navigation]
+Bottom Tab Bar: [Home] [Accounts] [Cards] [Profile]
+Top Bar: [Menu ☰] [Notifications 🔔]
+```
+
+## Next Step
+
+{project-root}/_bmad/bme/_designos/workflows/wireframe/steps/step-04-wireframe-sketch.md

package/_bmad/bme/_vortex/workflows/_deprecated/wireframe/steps/step-04-wireframe-sketch.md

@@ -0,0 +1,97 @@
+---
+step: 4
+workflow: wireframe
+title: Wireframe Sketch
+---
+
+# Step 4: Wireframe Sketch
+
+Time to create the low-fidelity wireframe layout using ASCII art.
+
+## Grid System
+
+- **Mobile:** 8pt grid, 16px margins
+- **Desktop:** 12-column grid, 24px gutters
+- **Alignment:** Everything snaps to grid
+
+## ASCII Wireframe Syntax
+
+```
+┌─────────────────────────────────┐  ← Top border
+│ ☰ Menu    Page Title       🔔   │  ← Header bar
+├─────────────────────────────────┤  ← Section divider
+│                                 │
+│        Main Content Area        │  ← Content section
+│                                 │
+│  ┌─────┐  ┌─────┐  ┌─────┐    │  ← Button row
+│  │ Btn1│  │ Btn2│  │ Btn3│    │
+│  └─────┘  └─────┘  └─────┘    │
+├─────────────────────────────────┤
+│ [Home] [Search] [Profile]      │  ← Bottom nav
+└─────────────────────────────────┘  ← Bottom border
+```
+
+## Component Placement
+
+1. **Header** (56-72px height)
+   - Logo/back button (left)
+   - Page title (center)
+   - Actions/notifications (right)
+
+2. **Content area**
+   - Primary content (hero, main action)
+   - Secondary content (supporting info)
+   - Tertiary content (metadata, help)
+
+3. **Navigation** (48-72px height)
+   - Bottom tabs (mobile)
+   - Sidebar (desktop)
+
+## Typography Hierarchy
+
+- **H1:** Screen title (24-32px)
+- **H2:** Section headers (20-24px)
+- **Body:** Content text (16px)
+- **Caption:** Metadata (12-14px)
+
+## Example: Mobile Dashboard
+
+```
+┌─────────────────────────────────┐
+│ ☰                          🔔   │ ← Header (56px)
+├─────────────────────────────────┤
+│                                 │
+│     Account Balance             │ ← H1 (Hero section)
+│      $12,458.32                 │ ← Large text
+│   Last updated: 2 min ago       │ ← Caption
+│                                 │
+├─────────────────────────────────┤
+│  ┌─────┐  ┌─────┐  ┌─────┐    │ ← Quick Actions
+│  │Trans│  │ Pay │  │Depo │    │   (3 buttons,
+│  │ fer │  │Bills│  │sit  │    │    100×48px each)
+│  └─────┘  └─────┘  └─────┘    │
+├─────────────────────────────────┤
+│ Recent Transactions         ↗   │ ← H2 + "See All"
+│ ┌───────────────────────────┐  │
+│ │ 🏪 Starbucks   -$5.42  →  │  │ ← Transaction item
+│ └───────────────────────────┘  │   (64px height)
+│ ┌───────────────────────────┐  │
+│ │ 💰 Salary    +$4,200   →  │  │
+│ └───────────────────────────┘  │
+│ ... (3 more items)              │
+│ [Load More Transactions]        │ ← Button
+├─────────────────────────────────┤
+│ [🏠] [💳] [📊] [👤]            │ ← Bottom tabs (72px)
+└─────────────────────────────────┘
+```
+
+## Your Turn
+
+Create your wireframe sketch using ASCII art. Include:
+- Header, content area, navigation
+- Component placements
+- Size annotations (px)
+
+## Next Step
+
+{project-root}/_bmad/bme/_designos/workflows/wireframe/steps/step-05-components.md