@soulcraft/kits 1.0.0

package/kits/persona-driven-strategy/skills/empathy-mapping/SKILL.md

@@ -0,0 +1,221 @@
+---
+id: empathy-mapping
+name: empathy-mapping
+description: Create empathy maps to understand user perspectives and experiences
+version: "1.0.0"
+type: invocable
+requiresVision: true
+requiresData: false
+---
+
+## Empathy Mapping Skill
+
+When the user invokes `/empathy`, help them create empathy maps that capture user perspectives, feelings, and motivations.
+
+### Invocation Patterns
+
+- `/empathy [persona]` - Create empathy map for persona
+- `/empathy session` - Guide empathy mapping workshop
+- `/empathy analyze` - Analyze existing empathy maps
+
+### What is an Empathy Map?
+
+A collaborative visualization used to articulate what we know about a particular type of user. It helps teams develop deep, shared understanding of users.
+
+### Empathy Map Quadrants
+
+**Says** (Quotes)
+- Direct quotes from research
+- What they tell others
+- How they describe their situation
+
+**Thinks** (Thoughts)
+- What occupies their mind
+- What they wonder about
+- Concerns they may not voice
+
+**Does** (Actions)
+- Observable behaviors
+- Activities and tasks
+- Physical actions
+
+**Feels** (Emotions)
+- Emotional state
+- Worries and fears
+- Hopes and aspirations
+
+### Output Format
+
+```markdown
+## Empathy Map: [Persona/User Type]
+
+### Context
+**Scenario**: [What situation are we mapping?]
+**Goal**: [What are they trying to accomplish?]
+
+---
+
+### SAYS
+*What do they literally say out loud?*
+
+> "[Quote 1]"
+
+> "[Quote 2]"
+
+> "[Quote 3]"
+
+**Themes**: [Common threads in what they say]
+
+---
+
+### THINKS
+*What might they be thinking but not saying?*
+
+- [Thought 1]
+- [Thought 2]
+- [Thought 3]
+
+**Questions on their mind**:
+- [Question 1]?
+- [Question 2]?
+
+**Worries they don't voice**:
+- [Worry 1]
+- [Worry 2]
+
+---
+
+### DOES
+*What actions and behaviors do we observe?*
+
+**Actions**:
+- [Action 1]
+- [Action 2]
+- [Action 3]
+
+**Habits/Patterns**:
+- [Pattern 1]
+- [Pattern 2]
+
+**Workarounds they've created**:
+- [Workaround]
+
+---
+
+### FEELS
+*What emotions are they experiencing?*
+
+**Positive Emotions**:
+- [Emotion]: [Trigger]
+
+**Negative Emotions**:
+- [Emotion]: [Trigger]
+
+**Emotional Journey**:
+[Start] → [Middle] → [End]
+
+---
+
+### PAINS
+*What frustrations, obstacles, or fears do they have?*
+
+1. **[Pain Point]**
+   - Severity: [High/Medium/Low]
+   - Frequency: [How often]
+
+2. **[Pain Point]**
+   - Severity: [High/Medium/Low]
+   - Frequency: [How often]
+
+### GAINS
+*What do they want to achieve? What would make them happy?*
+
+1. **[Desired Outcome]**
+   - Importance: [Critical/Important/Nice-to-have]
+
+2. **[Desired Outcome]**
+   - Importance: [Critical/Important/Nice-to-have]
+
+---
+
+### Key Insights
+1. [Insight 1]
+2. [Insight 2]
+3. [Insight 3]
+
+### Design Opportunities
+Based on this empathy map, we could:
+- [Opportunity 1]
+- [Opportunity 2]
+- [Opportunity 3]
+
+### Open Questions
+Things we still need to learn:
+- [Question 1]
+- [Question 2]
+```
+
+### Running an Empathy Mapping Session
+
+**Preparation**
+- Gather research artifacts
+- Prepare user quotes
+- Have observations ready
+- Invite cross-functional team
+
+**Process**
+1. Share research summary (10 min)
+2. Individual brainstorm on sticky notes (10 min)
+3. Share and cluster by quadrant (20 min)
+4. Identify patterns and insights (15 min)
+5. Define opportunities (15 min)
+
+**Materials**
+- Large paper or whiteboard
+- Sticky notes
+- Markers
+- Research summaries
+
+### Tips for Each Quadrant
+
+**Says**
+- Use actual quotes from research
+- Keep in their language
+- Note tone and emphasis
+- Don't paraphrase
+
+**Thinks**
+- Read between the lines
+- Note contradictions with "Says"
+- Consider unspoken concerns
+- Include hopes and fears
+
+**Does**
+- Focus on observable actions
+- Include digital behaviors
+- Note workarounds
+- Document frequency
+
+**Feels**
+- Name specific emotions
+- Connect to triggers
+- Note intensity
+- Map emotional journey
+
+### Common Mistakes
+
+- Making up data (must be research-based)
+- Confusing "Thinks" with "Says"
+- Surface-level observations
+- Not identifying contradictions
+- Stopping at the map (need insights)
+- Solo creation (should be collaborative)
+
+### When to Use
+
+- Beginning of project (understanding users)
+- Persona development
+- Feature planning
+- Marketing messaging
+- UX design decisions
+- Team alignment

package/kits/persona-driven-strategy/skills/journey-mapping/SKILL.md

@@ -0,0 +1,219 @@
+---
+id: journey-mapping
+name: journey-mapping
+description: Create user journey maps to visualize and improve experiences
+version: "1.0.0"
+type: invocable
+requiresVision: true
+requiresData: false
+---
+
+## User Journey Mapping Skill
+
+When the user invokes `/journey`, help them create comprehensive journey maps that visualize user experiences over time.
+
+### Invocation Patterns
+
+- `/journey [persona]` - Create journey map for persona
+- `/journey [scenario]` - Map specific user scenario
+- `/journey analyze` - Find opportunities in existing journey
+- `/journey compare` - Compare current vs. ideal journey
+
+### Journey Map Components
+
+**Stages**
+- Distinct phases of the experience
+- User's mental model of progress
+- Typically 4-7 stages
+
+**Actions**
+- What the user does at each stage
+- Tasks and activities
+- Decisions made
+
+**Touchpoints**
+- Where interaction occurs
+- Channels used
+- People encountered
+
+**Thoughts**
+- What's on user's mind
+- Questions they have
+- Considerations
+
+**Emotions**
+- How they feel
+- Emotional highs and lows
+- Confidence level
+
+**Pain Points**
+- Frustrations
+- Obstacles
+- Friction
+
+**Opportunities**
+- Ways to improve
+- Innovation areas
+- Quick wins
+
+### Output Format
+
+```markdown
+## User Journey Map: [Scenario Name]
+
+### Journey Overview
+**Persona**: [Name]
+**Scenario**: [What they're trying to accomplish]
+**Current State / Future State**: [Which this represents]
+**Scope**: [Start point] → [End point]
+
+---
+
+## Journey Stages
+
+### Stage 1: [Stage Name]
+**Duration**: [Typical time]
+
+**User Goal**: [What they want at this stage]
+
+**Actions**
+- [Action 1]
+- [Action 2]
+- [Action 3]
+
+**Touchpoints**
+| Channel | Touchpoint | Owner |
+|---------|------------|-------|
+| [Web/App/Phone/In-person] | [Specific touchpoint] | [Team] |
+
+**Thoughts**
+- "[What they're thinking]"
+- "[Questions they have]"
+
+**Emotions**: [😊/😐/😟] [Emotion name]
+**Satisfaction**: [1-5 or visual]
+
+**Pain Points**
+- ⚠️ [Pain point 1]
+- ⚠️ [Pain point 2]
+
+**Opportunities**
+- 💡 [Opportunity 1]
+- 💡 [Opportunity 2]
+
+---
+
+### Stage 2: [Stage Name]
+[Same format...]
+
+---
+
+### Stage 3: [Stage Name]
+[Same format...]
+
+---
+
+## Emotional Journey
+```
+     😊
+      │    ╭──╮
+ 😐   │   ╱    ╲   ╭──
+      │  ╱      ╰─╯
+ 😟   │─╯
+      └────────────────────
+       Stage1 Stage2 Stage3...
+```
+
+## Journey Summary
+
+### Overall Assessment
+| Metric | Rating |
+|--------|--------|
+| Overall satisfaction | [X/5] |
+| Effort required | [Low/Med/High] |
+| Likelihood to recommend | [X/10] |
+
+### Critical Pain Points (Priority)
+1. **[Pain Point]** at [Stage]
+   - Impact: [High/Med/Low]
+   - Effort to fix: [High/Med/Low]
+   - Recommendation: [Solution]
+
+2. **[Pain Point]** at [Stage]
+   - Impact: [High/Med/Low]
+   - Effort to fix: [High/Med/Low]
+   - Recommendation: [Solution]
+
+### Moments of Delight
+- 🌟 [Positive moment] at [Stage]
+
+### Key Opportunities
+| Opportunity | Stage | Impact | Effort | Priority |
+|-------------|-------|--------|--------|----------|
+| [Opp 1] | [Stage] | High | Low | **P1** |
+| [Opp 2] | [Stage] | Med | Med | P2 |
+
+### Recommended Actions
+**Quick Wins** (High impact, low effort):
+1. [Action]
+
+**Strategic Investments** (High impact, high effort):
+1. [Action]
+
+**Research Needed**:
+1. [Question to investigate]
+```
+
+### Journey Map Types
+
+**Current State**
+- How things work today
+- Based on research
+- Identifies problems
+
+**Future State**
+- Ideal experience
+- Aspirational
+- Guides design
+
+**Day in the Life**
+- Broader context
+- Full day, not just product
+- Holistic view
+
+**Service Blueprint**
+- Adds backstage actions
+- Shows supporting processes
+- Operational focus
+
+### Research for Journey Maps
+
+**Qualitative**
+- User interviews
+- Diary studies
+- Contextual inquiry
+- Support ticket analysis
+
+**Quantitative**
+- Analytics
+- Funnel data
+- Time-on-task
+- Satisfaction surveys
+
+### Common Stages (Customize for Context)
+
+**Awareness** → **Research** → **Evaluate** → **Purchase** → **Onboard** → **Use** → **Support** → **Renew/Leave**
+
+Or:
+
+**Trigger** → **Explore** → **Compare** → **Decide** → **Access** → **Use** → **Maintain** → **Advocate**
+
+### Best Practices
+
+- Base on real research
+- Include multiple perspectives
+- Focus on user's view
+- Identify emotion explicitly
+- Make actionable
+- Keep updated
+- Share widely

package/kits/persona-driven-strategy/skills/kit-expertise/SKILL.md

@@ -0,0 +1,81 @@
+---
+id: kit-expertise
+name: kit-expertise
+description: Domain expertise for Persona-Driven Strategy Suite - applied automatically when working in this kit
+version: "1.0.0"
+type: background
+requiresVision: false
+requiresData: false
+---
+
+## Your Role
+
+User Research and Strategy Consultant helping you create evidence-based personas and customer-centric strategies
+
+## Your Expertise
+
+- User persona development
+- Jobs-to-be-done framework
+- Customer journey mapping
+- Market segmentation
+- Empathy mapping
+- Value proposition design
+- Competitive analysis
+- Strategic planning
+
+## Your Approach
+
+Guide and teach the user, helping them understand concepts deeply
+
+## Things to Avoid
+
+- Creating fictional personas without research basis
+- Over-generalizing user segments
+- Ignoring edge cases and outliers
+- Making assumptions about user motivations
+
+## Domain Knowledge
+
+### Key Terms
+
+**persona**
+Archetypal representation of a user segment
+
+**jobs-to-be-done**
+Tasks users hire products to accomplish
+
+**pain points**
+Frustrations and obstacles users face
+
+**gains**
+Benefits and outcomes users desire
+
+**customer journey**
+Steps users take to accomplish goals
+
+**touchpoint**
+Interaction between user and product/service
+
+**empathy map**
+Tool for understanding user thoughts and feelings
+
+**value proposition**
+Promise of value delivered to users
+
+### Best Practices
+
+- Base personas on real user research
+- Include both demographics and psychographics
+- Document goals, frustrations, and motivations
+- Prioritize personas by business impact
+- Update personas as you learn more
+- Share personas across the organization
+
+### Common Mistakes to Avoid
+
+- Creating too many personas
+- Personas based on assumptions not research
+- Ignoring negative or edge-case users
+- Static personas that never update
+- Personas without clear use cases
+- Demographic-only profiles without motivations

package/kits/persona-driven-strategy/skills/persona-development/SKILL.md

@@ -0,0 +1,189 @@
+---
+id: persona-development
+name: persona-development
+description: Create detailed user personas based on research and data
+version: "1.0.0"
+type: invocable
+requiresVision: true
+requiresData: false
+---
+
+## Persona Development Skill
+
+When the user invokes `/persona`, help them create well-researched, useful user personas for their product or strategy.
+
+### Invocation Patterns
+
+- `/persona` - Create new persona from scratch
+- `/persona [segment]` - Create persona for specific segment
+- `/persona validate` - Validate/improve existing persona
+- `/persona compare` - Compare multiple personas
+
+### What Makes a Good Persona
+
+**Based on Research, Not Assumptions**
+- User interviews
+- Survey data
+- Analytics
+- Support tickets
+- Sales conversations
+
+**Specific Enough to Be Useful**
+- Not so broad it fits everyone
+- Not so narrow it's one person
+- Represents a meaningful segment
+
+**Actionable for Decisions**
+- Helps prioritize features
+- Guides messaging
+- Informs design choices
+
+### Output Format
+
+```markdown
+## User Persona: [Name]
+
+### Quick Reference
+**Name**: [Persona Name]
+**Role**: [Job title or role]
+**Segment**: [Customer segment]
+**Key Quote**: "[A phrase that captures their mindset]"
+
+---
+
+### Profile Photo & Demographics
+[Description for illustration purposes]
+- **Age**: [Range]
+- **Location**: [Type]
+- **Income**: [Range]
+- **Education**: [Level]
+- **Family**: [Situation]
+
+### Background
+[2-3 paragraph narrative about who they are, their situation, and context]
+
+### Goals
+**Primary Goal**: [What they ultimately want]
+**Secondary Goals**:
+1. [Goal]
+2. [Goal]
+3. [Goal]
+
+### Frustrations & Pain Points
+1. **[Pain Point]**: [Description]
+2. **[Pain Point]**: [Description]
+3. **[Pain Point]**: [Description]
+
+### Needs & Expectations
+- [Need 1]
+- [Need 2]
+- [Need 3]
+
+### Behaviors
+
+**Technology Usage**
+- Devices: [What they use]
+- Comfort level: [Savvy/Moderate/Basic]
+- Key apps/tools: [What they rely on]
+
+**Information Sources**
+- How they research: [Sources]
+- Trusted sources: [Who they trust]
+- Social media: [Usage]
+
+**Decision Making**
+- Process: [How they decide]
+- Influencers: [Who affects decisions]
+- Timeline: [Quick/Deliberate]
+
+### Day in the Life
+**Morning**: [Typical morning]
+**Workday**: [Typical work activities]
+**Evening**: [Typical evening]
+**Weekend**: [Typical weekend]
+
+### Journey with [Product/Service]
+**Awareness**: [How they discover solutions]
+**Consideration**: [How they evaluate]
+**Decision**: [What drives choice]
+**Use**: [How they use product]
+**Loyalty**: [What keeps them]
+
+### Objections & Concerns
+- [Concern 1]: [Why they might hesitate]
+- [Concern 2]: [Why they might hesitate]
+
+### Messages That Resonate
+- "[Message 1]"
+- "[Message 2]"
+- "[Message 3]"
+
+### Supporting Data
+| Attribute | Data Point | Source |
+|-----------|------------|--------|
+| [Attribute] | [Data] | [Research source] |
+
+---
+
+### Design Implications
+When designing for [Name]:
+- [Implication 1]
+- [Implication 2]
+- [Implication 3]
+```
+
+### Research Methods for Personas
+
+**Qualitative**
+- User interviews (1:1)
+- Focus groups
+- Contextual inquiry
+- Support call analysis
+- Social media listening
+
+**Quantitative**
+- Surveys
+- Analytics
+- Purchase data
+- Usage patterns
+- A/B test results
+
+### Persona Anti-Patterns
+
+**Elastic Persona**
+- Too vague to be useful
+- Describes everyone
+- No differentiating characteristics
+
+**Fantasy Persona**
+- Not based on research
+- Wishful thinking
+- Doesn't match real users
+
+**Demographic-Only Persona**
+- Just age, gender, location
+- Missing behaviors and goals
+- Not actionable
+
+**Neglected Persona**
+- Created but never used
+- Not updated
+- Not shared with team
+
+### Best Practices
+
+**Number of Personas**
+- 3-5 primary personas typically
+- More creates confusion
+- Cover key segments
+
+**Naming Conventions**
+- Memorable names
+- Often alliterative: "Marketing Mary"
+- Easy to reference
+
+**Keep Alive**
+- Review quarterly
+- Update with new research
+- Use in meetings
+- Reference in decisions