docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,150 @@
|
||||
# Business Goals Document Template
|
||||
|
||||
Complete template structure for 01-Business-Goals.md
|
||||
|
||||
---
|
||||
|
||||
## 1. Header
|
||||
|
||||
```markdown
|
||||
# Business Goals & Objectives
|
||||
|
||||
> Strategic goals and measurable objectives for [Project Name]
|
||||
|
||||
**Document:** Trigger Map - Business Goals
|
||||
**Created:** [Date]
|
||||
**Status:** COMPLETE
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 2. Vision Statement
|
||||
|
||||
```markdown
|
||||
## Vision
|
||||
|
||||
**[Insert vision statement from workshop]**
|
||||
|
||||
[Should be 1-2 sentences describing the ultimate goal/transformation]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 3. Business Objectives (3 Priority Tiers)
|
||||
|
||||
```markdown
|
||||
## Business Objectives
|
||||
|
||||
### ⭐ PRIMARY GOAL: [Title] (THE ENGINE)
|
||||
- **Statement:** [What we're building]
|
||||
- **Metric:** [How we measure it]
|
||||
- **Target:** [Specific number]
|
||||
- **Timeline:** [X months]
|
||||
- **Impact:** This drives ALL other objectives - this is the key to expansion
|
||||
|
||||
---
|
||||
|
||||
### 🚀 [SECONDARY GOALS CATEGORY] (Driven by [Primary Goal])
|
||||
|
||||
**Objective 1: [Title]**
|
||||
- **Statement:** [What we're achieving]
|
||||
- **Metric:** [How we measure]
|
||||
- **Target:** [Number]
|
||||
- **Timeline:** [X months from launch]
|
||||
|
||||
[Repeat for all secondary objectives: 2, 3, 4...]
|
||||
|
||||
---
|
||||
|
||||
### 🌟 [TERTIARY GOALS CATEGORY] (Real-World Benefits for Members)
|
||||
|
||||
**Note:** These are opportunities [Product] creates FOR the community members - [benefit description].
|
||||
|
||||
**Objective X: [Title]**
|
||||
- **Statement:** [What members get]
|
||||
- **Metric:** [How we measure member success]
|
||||
- **Target:** [Number]
|
||||
- **Timeline:** [X months]
|
||||
- **Benefit to Members:** [Career/personal growth impact]
|
||||
|
||||
[Repeat for all tertiary objectives]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 4. The Flywheel Section
|
||||
|
||||
```markdown
|
||||
## The Flywheel: How Goals Connect
|
||||
|
||||
**THE ENGINE (Priority #1):**
|
||||
- [Primary goal number] [primary goal description]
|
||||
- Timeline: [X] months
|
||||
- These [users] [action that drives everything]
|
||||
- They create the flywheel that drives ALL other objectives
|
||||
|
||||
**[Secondary Category] (Priority #2):**
|
||||
- Driven BY the [primary goal achievers]
|
||||
- [List key targets with numbers]
|
||||
- Timeline: [X] months
|
||||
- Focus: [What this tier achieves]
|
||||
|
||||
**[Tertiary Category] (Priority #3):**
|
||||
- Real-world benefits FOR community members
|
||||
- [List key opportunities]
|
||||
- Timeline: [X] months
|
||||
- **Key benefit**: [How members' lives improve]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 5. Success Metrics Alignment
|
||||
|
||||
```markdown
|
||||
## Success Metrics Alignment
|
||||
|
||||
### How Trigger Map Connects to Objectives (Properly Prioritized):
|
||||
|
||||
**⭐ PRIMARY: Creating Awesome [Users] Who Become [Champions] → Achieves:**
|
||||
- ✅ **[Number] [champions]** (THE ENGINE - [Persona] becomes one of them naturally)
|
||||
- ✅ [Action 1]
|
||||
- ✅ [Action 2]
|
||||
- ✅ [Natural outcome]
|
||||
- **Timeline: [X] months**
|
||||
- **This drives ALL other objectives**
|
||||
|
||||
**🚀 SECONDARY: [Champions] Drive [Product] Adoption → Achieves:**
|
||||
- ✅ [Objective 1] ([champions] spread the word)
|
||||
- ✅ [Objective 2] ([champions] demonstrate value)
|
||||
- ✅ [Objective 3] ([champions] create engagement)
|
||||
- **Timeline: [X] months**
|
||||
|
||||
**🌟 TERTIARY: [Product] Success Creates Opportunities for Community → Achieves:**
|
||||
- ✅ [Opportunity 1] (members [benefit])
|
||||
- ✅ [Opportunity 2] (members [benefit])
|
||||
- ✅ [Opportunity 3] (members [benefit])
|
||||
- **Timeline: [X] months**
|
||||
- **Benefit: [Impact on members' lives/careers]**
|
||||
|
||||
**The Trigger Map IS the Strategic Foundation - And Prioritization Matters**
|
||||
|
||||
The page must empower [Primary Persona] → make [them] awesome → [they] naturally become [champions] → [champions] drive adoption → adoption creates opportunities for all members.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Related Documents Footer
|
||||
|
||||
```markdown
|
||||
## Related Documents
|
||||
|
||||
- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
|
||||
- **[02-[Primary].md](02-[Primary].md)** - Primary persona
|
||||
- **[03-[Secondary].md](03-[Secondary].md)** - Secondary persona
|
||||
- **[04-[Tertiary].md](04-[Tertiary].md)** - Tertiary persona [if exists]
|
||||
- **[05-Key-Insights.md](05-Key-Insights.md)** - Strategic implications
|
||||
|
||||
---
|
||||
|
||||
_Back to [Trigger Map](00-trigger-map.md)_
|
||||
```
|
||||
@@ -0,0 +1,222 @@
|
||||
# Key Insights Document Structure Guide
|
||||
|
||||
**Complete template for generating 05-Key-Insights.md**
|
||||
|
||||
---
|
||||
|
||||
## 1. Header
|
||||
|
||||
```markdown
|
||||
# Key Insights & Strategic Implications
|
||||
|
||||
> How the Trigger Map informs design and development decisions
|
||||
|
||||
**Document:** Trigger Map - Key Insights
|
||||
**Created:** [Date]
|
||||
**Status:** COMPLETE
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 2. The Flywheel Section
|
||||
|
||||
```markdown
|
||||
## The Flywheel: [X] [Champions] Drive Everything
|
||||
|
||||
**THE ENGINE (Priority #1):**
|
||||
- [X] [champions] are THE PRIMARY GOAL
|
||||
- Timeline: [X] months
|
||||
- These [description of what makes them champions]
|
||||
- They create the flywheel that drives ALL other objectives
|
||||
|
||||
**[Product] Adoption (Priority #2):**
|
||||
- Driven BY the [X] [champions] spreading the word
|
||||
- [List key adoption targets with numbers]
|
||||
- Timeline: [X] months
|
||||
- Focus: [What this tier achieves]
|
||||
|
||||
**Community Opportunities (Priority #3):**
|
||||
- Real-world benefits FOR community members
|
||||
- [List key opportunities]
|
||||
- Timeline: [X] months
|
||||
- **Key benefit**: [How members' lives/careers improve]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 3. Primary Development Focus
|
||||
|
||||
```markdown
|
||||
## Primary Development Focus
|
||||
|
||||
1. **Create Awesome [Users] Who Become [Champions]** - [Primary persona] is the profile who becomes one of the [X]
|
||||
2. **[Key Transformation Need]** - Address [primary persona]'s core need to move from [before] to [after]
|
||||
3. **[Core Capability Building]** - [Specific approach to building confidence/skill]
|
||||
4. **[Validation Need]** - Show [secondary persona] how [product] delivers [value]
|
||||
5. **[Support Need]** - Prove to [tertiary persona] that [benefit] reduces [pain]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 4. Critical Success Factors
|
||||
|
||||
```markdown
|
||||
## Critical Success Factors
|
||||
|
||||
- **[Factor 1]**: [Description] (the [key element] in action)
|
||||
- **[Factor 2]**: [Clear steps description]
|
||||
- **[Factor 3]**: [Proof element] ([specific example])
|
||||
- **[Factor 4]**: [Access description]
|
||||
- **[Factor 5]**: [Scope description] (not just [limitation])
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 5. Design Implications
|
||||
|
||||
```markdown
|
||||
## Design Implications
|
||||
|
||||
### Content Priorities Based on Triggers:
|
||||
|
||||
**[Section 1] Must:**
|
||||
- [Requirement 1]
|
||||
- [Requirement 2]
|
||||
- [Requirement 3]
|
||||
|
||||
**[Section 2] Must:**
|
||||
- [Requirement 1]
|
||||
- [Requirement 2]
|
||||
- [Requirement 3]
|
||||
|
||||
**[Section 3] Must:**
|
||||
- [Requirement 1]
|
||||
- [Requirement 2]
|
||||
- [Requirement 3]
|
||||
|
||||
**[Section 4] Must:**
|
||||
- [Requirement 1]
|
||||
- [Requirement 2]
|
||||
- [Requirement 3]
|
||||
|
||||
**[Section 5] Must:**
|
||||
- [Requirement 1]
|
||||
- [Requirement 2]
|
||||
- [Requirement 3]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Emotional Transformation Goals
|
||||
|
||||
```markdown
|
||||
## Emotional Transformation Goals
|
||||
|
||||
- **[Goal 1]**: "[First-person statement of transformation]"
|
||||
- **[Goal 2]**: "[First-person statement about capability]"
|
||||
- **[Goal 3]**: "[First-person statement about confidence]"
|
||||
- **[Goal 4]**: "[First-person statement about impact]"
|
||||
- **[Goal 5]**: "[First-person statement about identity]"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 7. Design Focus Statement
|
||||
|
||||
```markdown
|
||||
## Design Focus Statement
|
||||
|
||||
**The [Product] [Page/Experience] transforms [target users] from [before state] into [after state] who [key transformation] as a [metaphor], not a [negative metaphor].**
|
||||
|
||||
**Primary Design Target:** [Primary Persona Name] ([Role])
|
||||
|
||||
**Must Address (Critical for Conversion):**
|
||||
1. [Fear 1] → [Solution approach]
|
||||
2. [Fear 2] → [Solution approach]
|
||||
3. [Fear 3] → [Solution approach]
|
||||
4. [Want 1] → [Delivery approach]
|
||||
5. [Want 2] → [Delivery approach]
|
||||
|
||||
**Should Address (Supporting Conversion):**
|
||||
1. [Secondary persona] needs [thing] → [Approach]
|
||||
2. [Tertiary persona] needs [thing] → [Approach]
|
||||
3. [Community proof element] → [Approach]
|
||||
4. [Learning curve concern] → [Approach]
|
||||
5. [Integration concern] → [Approach]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 8. Development Phases
|
||||
|
||||
```markdown
|
||||
## Development Phases
|
||||
|
||||
### **First Deliverable: [Product Name] [Initial Release]**
|
||||
Focus on empowering [primary persona] from [before] to awesome [after] who naturally becomes [champion]:
|
||||
- **[Section 1]** - [Key message/approach]
|
||||
- **[Section 2]** - [Key message/approach]
|
||||
- **[Section 3]** - [Key message/approach]
|
||||
- **[Section 4]** - [Key message/approach]
|
||||
- **[Section 5]** - [Key message/approach]
|
||||
- **[Section 6]** - [Key message/approach]
|
||||
- **[Section 7]** - [Key message/approach]
|
||||
|
||||
### **Future Phases: Additional Content**
|
||||
- **Phase 2**: [Next priority]
|
||||
- **Phase 3**: [Next priority]
|
||||
- **Phase 4**: [Next priority]
|
||||
- **Phase 5**: [Next priority]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 9. Related Documents Footer
|
||||
|
||||
```markdown
|
||||
## Related Documents
|
||||
|
||||
- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
|
||||
- **[01-Business-Goals.md](01-Business-Goals.md)** - Objectives and metrics
|
||||
- **[02-[Primary].md](02-[Primary].md)** - Primary persona
|
||||
- **[03-[Secondary].md](03-[Secondary].md)** - Secondary persona
|
||||
- **[04-[Tertiary].md](04-[Tertiary].md)** - Tertiary persona [if exists]
|
||||
- **[06-Design-Implications.md](06-Design-Implications.md)** - Detailed design requirements [if exists]
|
||||
|
||||
---
|
||||
|
||||
_Back to [Trigger Map](00-trigger-map.md)_
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template Guidelines
|
||||
|
||||
**Tone:**
|
||||
- Actionable and specific
|
||||
- "Create awesome" language throughout
|
||||
- Links back to workshop outputs
|
||||
|
||||
**Focus:**
|
||||
- PRIMARY persona gets most attention in "Must Address"
|
||||
- Secondary and tertiary get "Should Address"
|
||||
- Transformation is central theme
|
||||
|
||||
**Design Implications:**
|
||||
- Organized by page/experience sections
|
||||
- Each section has clear "must do" items
|
||||
- Tied to specific fears/wants from personas
|
||||
|
||||
**Emotional Goals:**
|
||||
- First-person statements
|
||||
- Show identity shift
|
||||
- Positive and empowering
|
||||
|
||||
**Expected Length:**
|
||||
- ~145-150 lines for complete document
|
||||
- Use specific examples from trigger map
|
||||
- Keep actionable and scannable
|
||||
|
||||
---
|
||||
|
||||
_Complete structure guide for Step 04: Generate Key Insights_
|
||||
@@ -0,0 +1,262 @@
|
||||
# Micro Instructions: Generate Mermaid Trigger Map Diagram
|
||||
|
||||
**Purpose:** Create visually appealing, professional Mermaid flowchart diagrams for trigger maps
|
||||
|
||||
---
|
||||
|
||||
## Format Requirements
|
||||
|
||||
### 1. Mermaid Configuration
|
||||
```
|
||||
%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%
|
||||
```
|
||||
- Always use Inter/system-ui font
|
||||
- Set fontSize to 14px
|
||||
- Use base theme
|
||||
|
||||
### 2. Flowchart Direction
|
||||
```
|
||||
flowchart LR
|
||||
```
|
||||
- Always use left-to-right (LR) direction
|
||||
- Business goals on left → Platform center → Target groups → Driving forces on right
|
||||
|
||||
### 3. Node Content Formatting
|
||||
|
||||
**Every node must:**
|
||||
- Start with `<br/>` for top padding
|
||||
- End with `<br/><br/>` for bottom padding
|
||||
- Use `<br/>` for line breaks (not multiple spaces)
|
||||
- Include emoji at the start of the title
|
||||
|
||||
**Example node structure:**
|
||||
```
|
||||
NodeID["<br/>🎯 TITLE<br/><br/>Line 1<br/>Line 2<br/>Line 3<br/><br/>"]
|
||||
```
|
||||
|
||||
### 4. Business Goals Nodes (Left Column)
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
BG1["<br/>🌟 WDS VISION<br/><br/>Point 1<br/>Point 2<br/>Point 3<br/><br/>"]
|
||||
BG2["<br/>📊 CORE OBJECTIVES<br/><br/>Point 1<br/>Point 2<br/>Point 3<br/><br/>"]
|
||||
```
|
||||
|
||||
**Rules:**
|
||||
- Use BG0, BG1, BG2, etc. as node IDs
|
||||
- Include relevant emoji (🌟 for vision, 📊 for objectives, 🚀 for growth, etc.)
|
||||
- List 3-5 key points per goal
|
||||
- Keep titles in ALL CAPS
|
||||
|
||||
### 5. Platform Node (Center)
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
PLATFORM["<br/>🎨 PLATFORM NAME<br/><br/>Tagline or category<br/><br/>Transformation statement<br/>that spans multiple lines<br/>describing the core change<br/><br/>"]
|
||||
```
|
||||
|
||||
**Rules:**
|
||||
- Single node ID: PLATFORM
|
||||
- Include platform emoji
|
||||
- Show tagline/category
|
||||
- Include transformation/value statement
|
||||
- Break long text into multiple lines
|
||||
|
||||
### 6. Target Group Nodes
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
TG1["<br/>🎯 PERSONA NAME<br/>PRIORITY LEVEL<br/><br/>Trait 1<br/>Trait 2<br/>Trait 3<br/><br/>"]
|
||||
```
|
||||
|
||||
**Rules:**
|
||||
- Use TG0, TG1, TG2, etc. as node IDs
|
||||
- Include persona-specific emoji
|
||||
- Show priority (PRIMARY TARGET, SECONDARY TARGET, etc.)
|
||||
- List 3-4 key profile traits
|
||||
- Keep persona name in ALL CAPS
|
||||
|
||||
### 7. Driving Forces Nodes
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
DF1["<br/>🎯 PERSONA'S DRIVERS<br/><br/>WANTS<br/>✅ Positive driver 1<br/>✅ Positive driver 2<br/>✅ Positive driver 3<br/><br/>FEARS<br/>❌ Negative driver 1<br/>❌ Negative driver 2<br/>❌ Negative driver 3<br/><br/>"]
|
||||
```
|
||||
|
||||
**Rules:**
|
||||
- Use DF0, DF1, DF2, etc. matching TG IDs
|
||||
- Use same emoji as corresponding persona
|
||||
- Add "PERSONA'S DRIVERS" in ALL CAPS
|
||||
- Section headers: "WANTS" and "FEARS" (no emojis on headers)
|
||||
- ✅ emoji before each positive driver
|
||||
- ❌ emoji before each negative driver
|
||||
- Exactly 3 drivers per category (top 3 only)
|
||||
- Blank line between sections
|
||||
|
||||
### 8. Connections
|
||||
|
||||
**Required connections:**
|
||||
```
|
||||
%% Business Goals to Platform
|
||||
BG0 --> PLATFORM
|
||||
BG1 --> PLATFORM
|
||||
BG2 --> PLATFORM
|
||||
|
||||
%% Platform to Target Groups
|
||||
PLATFORM --> TG0
|
||||
PLATFORM --> TG1
|
||||
PLATFORM --> TG2
|
||||
|
||||
%% Target Groups to Driving Forces
|
||||
TG0 --> DF0
|
||||
TG1 --> DF1
|
||||
TG2 --> DF2
|
||||
```
|
||||
|
||||
**Rules:**
|
||||
- All business goals connect to platform
|
||||
- Platform connects to all target groups
|
||||
- Each target group connects to its driving forces
|
||||
- Use simple arrows (-->), no fancy styling
|
||||
|
||||
### 9. Styling Classes
|
||||
|
||||
**Required classes:**
|
||||
```css
|
||||
classDef businessGoal fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
|
||||
classDef platform fill:#e5e7eb,color:#111827,stroke:#9ca3af,stroke-width:3px
|
||||
classDef targetGroup fill:#f9fafb,color:#1f2937,stroke:#d1d5db,stroke-width:2px
|
||||
classDef drivingForces fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
|
||||
```
|
||||
|
||||
**Application:**
|
||||
```
|
||||
class BG0,BG1,BG2 businessGoal
|
||||
class PLATFORM platform
|
||||
class TG0,TG1,TG2 targetGroup
|
||||
class DF0,DF1,DF2 drivingForces
|
||||
```
|
||||
|
||||
**Rules:**
|
||||
- Always use these exact colors (light grays with dark text)
|
||||
- Business goals: lightest gray (#f3f4f6)
|
||||
- Platform: medium gray (#e5e7eb) with thicker border (3px)
|
||||
- Target groups: near white (#f9fafb)
|
||||
- Driving forces: light gray (#f3f4f6)
|
||||
- Text color: dark gray (#1f2937 or #111827)
|
||||
- Borders: light gray (#d1d5db or #9ca3af)
|
||||
|
||||
---
|
||||
|
||||
## Complete Example Template
|
||||
|
||||
```mermaid
|
||||
%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%
|
||||
flowchart LR
|
||||
%% Business Goals
|
||||
BG0["<br/>🌟 VISION<br/><br/>Vision statement line 1<br/>Vision statement line 2<br/>Vision statement line 3<br/><br/>"]
|
||||
BG1["<br/>📊 OBJECTIVES<br/><br/>Objective 1<br/>Objective 2<br/>Objective 3<br/><br/>"]
|
||||
|
||||
%% Platform
|
||||
PLATFORM["<br/>🎨 PRODUCT NAME<br/><br/>Product category or tagline<br/><br/>Transformation statement<br/>describing the change<br/><br/>"]
|
||||
|
||||
%% Target Groups
|
||||
TG0["<br/>🎯 PERSONA ONE<br/>PRIMARY TARGET<br/><br/>Profile trait 1<br/>Profile trait 2<br/>Profile trait 3<br/><br/>"]
|
||||
TG1["<br/>💼 PERSONA TWO<br/>SECONDARY TARGET<br/><br/>Profile trait 1<br/>Profile trait 2<br/>Profile trait 3<br/><br/>"]
|
||||
|
||||
%% Driving Forces
|
||||
DF0["<br/>🎯 PERSONA ONE'S DRIVERS<br/><br/>WANTS<br/>✅ Positive driver 1<br/>✅ Positive driver 2<br/>✅ Positive driver 3<br/><br/>FEARS<br/>❌ Negative driver 1<br/>❌ Negative driver 2<br/>❌ Negative driver 3<br/><br/>"]
|
||||
|
||||
DF1["<br/>💼 PERSONA TWO'S DRIVERS<br/><br/>WANTS<br/>✅ Positive driver 1<br/>✅ Positive driver 2<br/>✅ Positive driver 3<br/><br/>FEARS<br/>❌ Negative driver 1<br/>❌ Negative driver 2<br/>❌ Negative driver 3<br/><br/>"]
|
||||
|
||||
%% Connections
|
||||
BG0 --> PLATFORM
|
||||
BG1 --> PLATFORM
|
||||
PLATFORM --> TG0
|
||||
PLATFORM --> TG1
|
||||
TG0 --> DF0
|
||||
TG1 --> DF1
|
||||
|
||||
%% Styling
|
||||
classDef businessGoal fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
|
||||
classDef platform fill:#e5e7eb,color:#111827,stroke:#9ca3af,stroke-width:3px
|
||||
classDef targetGroup fill:#f9fafb,color:#1f2937,stroke:#d1d5db,stroke-width:2px
|
||||
classDef drivingForces fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
|
||||
|
||||
class BG0,BG1 businessGoal
|
||||
class PLATFORM platform
|
||||
class TG0,TG1 targetGroup
|
||||
class DF0,DF1 drivingForces
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Emoji Selection Guide
|
||||
|
||||
### Business Goals
|
||||
- 🌟 Vision
|
||||
- 📊 Objectives/Metrics
|
||||
- 🚀 Growth/Expansion
|
||||
- 💰 Revenue/Business
|
||||
- 🤝 Partnerships/Community
|
||||
- 🎯 Goals/Targets
|
||||
|
||||
### Personas
|
||||
- 🎯 Strategic/Primary personas
|
||||
- 💼 Business/Leadership personas
|
||||
- 💻 Technical/Developer personas
|
||||
- 👥 Team/Group personas
|
||||
- 🎨 Creative/Designer personas
|
||||
- 📱 User/Customer personas
|
||||
|
||||
### Platform
|
||||
- 🎨 Design/Creative products
|
||||
- 💻 Software/Tech products
|
||||
- 📱 Mobile/App products
|
||||
- 🛠️ Tools/Utilities
|
||||
- 📊 Analytics/Data products
|
||||
- 🤖 AI/Automation products
|
||||
|
||||
---
|
||||
|
||||
## Quality Checklist
|
||||
|
||||
Before finalizing diagram, verify:
|
||||
|
||||
- [ ] Mermaid config includes custom font and fontSize
|
||||
- [ ] All nodes start with `<br/>` and end with `<br/><br/>`
|
||||
- [ ] All titles are in ALL CAPS
|
||||
- [ ] Each persona has matching emoji in both TG and DF nodes
|
||||
- [ ] Exactly 3 positive drivers per persona (with ✅)
|
||||
- [ ] Exactly 3 negative drivers per persona (with ❌)
|
||||
- [ ] "WANTS" and "FEARS" headers have no emojis
|
||||
- [ ] All connections are present (goals→platform→groups→forces)
|
||||
- [ ] Light gray styling with dark text applied
|
||||
- [ ] Platform has thicker border (3px)
|
||||
- [ ] No syntax errors or missing brackets
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes to Avoid
|
||||
|
||||
❌ **Don't:**
|
||||
- Use multiple spaces for alignment (use `<br/>` only)
|
||||
- Mix HTML tags (bold, italic) - keep plain text
|
||||
- Forget padding (`<br/>`) at top and bottom
|
||||
- Use colors other than light grays
|
||||
- Add emojis to "WANTS" and "FEARS" headers
|
||||
- Include more than 3 drivers per category
|
||||
- Use lowercase in titles
|
||||
|
||||
✅ **Do:**
|
||||
- Use `<br/>` for all line breaks
|
||||
- Keep consistent spacing (blank lines between sections)
|
||||
- Match emojis between personas and their drivers
|
||||
- Use exactly 3 drivers per category
|
||||
- Apply consistent styling to all nodes
|
||||
- Test diagram renders correctly
|
||||
|
||||
---
|
||||
|
||||
**This format creates professional, scannable trigger maps that clearly communicate strategic insights at a glance.**
|
||||
|
||||
212
_bmad/wds/workflows/2-trigger-mapping/data/quality-checklist.md
Normal file
212
_bmad/wds/workflows/2-trigger-mapping/data/quality-checklist.md
Normal file
@@ -0,0 +1,212 @@
|
||||
# Quality Check & Verification Checklist
|
||||
|
||||
**Complete checklist for verifying trigger map documentation quality**
|
||||
|
||||
---
|
||||
|
||||
## 1. File Structure Check
|
||||
|
||||
- [ ] `00-trigger-map.md` exists
|
||||
- [ ] `01-Business-Goals.md` exists
|
||||
- [ ] `02-[Primary Persona].md` exists
|
||||
- [ ] `03-[Secondary Persona].md` exists
|
||||
- [ ] `04-[Tertiary Persona].md` exists (if applicable)
|
||||
- [ ] `05-Key-Insights.md` exists
|
||||
- [ ] `06-Feature-Impact.md` exists (if Feature Impact workshop was completed)
|
||||
- [ ] All files use consistent naming pattern
|
||||
|
||||
---
|
||||
|
||||
## 2. Mermaid Diagram Quality
|
||||
|
||||
**In `00-trigger-map.md`:**
|
||||
|
||||
- [ ] Diagram renders without errors
|
||||
- [ ] BG0 (PRIMARY GOAL) has gold highlighting (`primaryGoal` class)
|
||||
- [ ] All nodes have proper padding (`<br/>` at start and end)
|
||||
- [ ] Emojis present: ✅ for wants, ❌ for fears
|
||||
- [ ] Exactly 3 drivers per persona
|
||||
- [ ] Connections flow correctly: BG→PLATFORM→TG→DF
|
||||
- [ ] Styling section includes all 5 classes (primaryGoal, businessGoal, platform, targetGroup, drivingForces)
|
||||
- [ ] Font family set to Inter or system-ui
|
||||
|
||||
---
|
||||
|
||||
## 3. Content Consistency
|
||||
|
||||
**Across ALL documents:**
|
||||
|
||||
- [ ] PRIMARY GOAL consistently labeled as "THE ENGINE"
|
||||
- [ ] Transformation journey clearly described
|
||||
- [ ] Timeline numbers match across documents
|
||||
- [ ] Target numbers (50 champions, 5000 users, etc.) are consistent
|
||||
- [ ] Persona names spelled consistently
|
||||
- [ ] Product name consistent throughout
|
||||
|
||||
---
|
||||
|
||||
## 4. Language Check
|
||||
|
||||
**Verify empowering language:**
|
||||
|
||||
- [ ] "Create awesome [users]" NOT "convert users"
|
||||
- [ ] "Naturally become [champions]" NOT "make them champions"
|
||||
- [ ] "Community Opportunities" emphasize benefits FOR members
|
||||
- [ ] No pushy or transactional language
|
||||
- [ ] Transformation language is positive and organic
|
||||
|
||||
---
|
||||
|
||||
## 5. Cross-Reference Verification
|
||||
|
||||
**Check links in each document:**
|
||||
|
||||
**00-trigger-map.md:**
|
||||
- [ ] Links to 01-Business-Goals.md
|
||||
- [ ] Links to all persona docs (02, 03, 04...)
|
||||
- [ ] Links to 05-Key-Insights.md
|
||||
- [ ] All links use correct file names
|
||||
|
||||
**01-Business-Goals.md:**
|
||||
- [ ] Links back to 00-trigger-map.md
|
||||
- [ ] Links to all persona docs
|
||||
- [ ] Links to 05-Key-Insights.md
|
||||
|
||||
**Persona documents (02, 03, 04...):**
|
||||
- [ ] Each links back to 00-trigger-map.md
|
||||
- [ ] Each links to OTHER persona docs
|
||||
- [ ] Each links to 05-Key-Insights.md
|
||||
|
||||
**05-Key-Insights.md:**
|
||||
- [ ] Links back to 00-trigger-map.md
|
||||
- [ ] Links to 01-Business-Goals.md
|
||||
- [ ] Links to all persona docs
|
||||
|
||||
**06-Feature-Impact.md (if exists):**
|
||||
- [ ] Links back to 00-trigger-map.md
|
||||
- [ ] Links to 01-Business-Goals.md
|
||||
- [ ] Links to all persona docs
|
||||
- [ ] Links to 05-Key-Insights.md
|
||||
|
||||
---
|
||||
|
||||
## 6. Persona Document Completeness
|
||||
|
||||
**For EACH persona document, verify:**
|
||||
|
||||
- [ ] Has all 13 sections (header through related docs)
|
||||
- [ ] Profile summary is compelling (1-2 paragraphs)
|
||||
- [ ] Background section tells their story
|
||||
- [ ] Current situation shows challenges
|
||||
- [ ] Psychological profile reveals motivations
|
||||
- [ ] **6 driving forces** (3 wants + 3 fears) each with Product Promise/Answer
|
||||
- [ ] Transformation journey (especially PRIMARY)
|
||||
- [ ] Strategic triangle diagram present
|
||||
- [ ] Role clearly explained
|
||||
- [ ] Impact on business goals shown
|
||||
- [ ] Related documents footer complete
|
||||
|
||||
---
|
||||
|
||||
## 7. Hub Document (00) On-Page Content
|
||||
|
||||
**Verify hub has on-page summaries for:**
|
||||
|
||||
- [ ] Transformation clearly stated
|
||||
- [ ] Flywheel explained (3 tiers)
|
||||
- [ ] Business Strategy section with key points
|
||||
- [ ] Each persona with profile + drivers visible
|
||||
- [ ] Strategic Implications with key focus areas
|
||||
- [ ] "How to Read" explanation present
|
||||
- [ ] Total length ~220-250 lines
|
||||
|
||||
---
|
||||
|
||||
## 8. Business Goals Document (01) Completeness
|
||||
|
||||
- [ ] Vision statement present
|
||||
- [ ] PRIMARY GOAL clearly marked as THE ENGINE
|
||||
- [ ] SECONDARY goals grouped and explained
|
||||
- [ ] TERTIARY goals emphasize member benefits
|
||||
- [ ] Each objective has: Statement, Metric, Target, Timeline, Impact/Benefit
|
||||
- [ ] Flywheel section explains priorities
|
||||
- [ ] Success metrics show persona connections
|
||||
- [ ] Total length ~150-160 lines
|
||||
|
||||
---
|
||||
|
||||
## 9. Key Insights Document (05) Completeness
|
||||
|
||||
- [ ] Flywheel priorities explained
|
||||
- [ ] Primary Development Focus lists 5 areas
|
||||
- [ ] Critical Success Factors (3-5 items)
|
||||
- [ ] Design Implications by section (5+ sections)
|
||||
- [ ] Emotional Transformation Goals in first person
|
||||
- [ ] Design Focus Statement present
|
||||
- [ ] Development Phases outlined
|
||||
- [ ] Total length ~145-155 lines
|
||||
|
||||
---
|
||||
|
||||
## 10. Feature Impact Document (06) Completeness (If Exists)
|
||||
|
||||
- [ ] Scoring system clearly explained
|
||||
- [ ] Primary persona weighted higher (5/3/1 vs 3/1/0)
|
||||
- [ ] Feature table with scores for all personas
|
||||
- [ ] Must Have / Consider / Defer categories
|
||||
- [ ] Strategic rationale explains prioritization
|
||||
- [ ] Connection to business goals shown
|
||||
- [ ] Development phases aligned with flywheel
|
||||
- [ ] Each feature ties to specific persona drivers
|
||||
|
||||
---
|
||||
|
||||
## 11. Priority Tier Consistency
|
||||
|
||||
**Verify throughout all documents:**
|
||||
|
||||
- [ ] ⭐ PRIMARY GOAL always uses star emoji + gold in diagram
|
||||
- [ ] 🚀 SECONDARY uses rocket emoji
|
||||
- [ ] 🌟 TERTIARY uses sparkle emoji
|
||||
- [ ] PRIMARY always described as "THE ENGINE"
|
||||
- [ ] SECONDARY always "driven by" PRIMARY
|
||||
- [ ] TERTIARY always "benefits FOR members"
|
||||
|
||||
---
|
||||
|
||||
## 12. Driving Forces Quality
|
||||
|
||||
**For each persona's 6 driving forces:**
|
||||
|
||||
- [ ] Each want has **[Product] Promise:**
|
||||
- [ ] Each fear has **[Product] Answer:**
|
||||
- [ ] Promises/Answers are specific (not generic)
|
||||
- [ ] They show HOW product addresses the driver
|
||||
- [ ] Language is empowering and actionable
|
||||
|
||||
---
|
||||
|
||||
## 13. Formatting Check
|
||||
|
||||
- [ ] Markdown renders correctly
|
||||
- [ ] Headers use proper hierarchy (# ## ###)
|
||||
- [ ] Code blocks use correct syntax
|
||||
- [ ] Emojis display properly
|
||||
- [ ] Lists are formatted consistently
|
||||
- [ ] Links are properly formatted `[text](file.md)`
|
||||
- [ ] Horizontal rules (`---`) used appropriately
|
||||
|
||||
---
|
||||
|
||||
## Error Correction Process
|
||||
|
||||
If any checklist item fails:
|
||||
|
||||
1. **Identify which document(s) need fixing**
|
||||
2. **Re-read the specific step instructions**
|
||||
3. **Make corrections**
|
||||
4. **Re-verify the corrected sections**
|
||||
|
||||
---
|
||||
|
||||
_Complete quality checklist for Step 05: Quality Check & Verification_
|
||||
Reference in New Issue
Block a user