@comfanion/workflow 4.38.4-dev.1 → 4.39.0

package/src/opencode/skills/methodologies/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: methodologies
-description: Use when applying Five Whys, Empathy Mapping, Journey Mapping, or other analysis methods
+description: Apply analysis methodologies - Five Whys (root cause), Empathy Mapping (user feelings), Journey Mapping (user flow), Fishbone (cause-effect). Use when analyzing problems, understanding users, mapping journeys, or when user mentions "Five Whys", "root cause", "empathy map", "journey map", "user analysis", or "problem analysis".
 license: MIT
 compatibility: opencode
 metadata:
@@ -10,377 +10,114 @@ metadata:
 
 # Methodologies Skill
 
-> **Purpose**: Structured methods for requirements, analysis, and problem-solving
-> **Used by**: Analyst, PM, Architect, Researcher
-
----
-
-## By Agent Role
-
-| Agent | Primary Methods |
-|-------|-----------------|
-| **Analyst (Mary)** | User Interviews, Empathy Mapping, Journey Mapping, Affinity Clustering, Five Whys, Fishbone |
-| **PM (John)** | Problem Framing, HMW, POV Statement, JTBD, Brainstorming, SCAMPER |
-| **Architect (Winston)** | Systems Thinking, Fishbone, Is/Is Not Analysis, Decision Matrix |
-| **Researcher (Alex)** | Analogous Inspiration, Five Whys, Systems Thinking, Is/Is Not |
-
----
-
-## EMPATHIZE Methods (Analyst)
-
-### User Interviews
-**Purpose**: Deep conversations to understand user needs, experiences, and pain points
-
-**Prompts**:
-- What brings you here today?
-- Walk me through a recent experience
-- What frustrates you most?
-- What would make this easier?
-- Tell me more about that
-
-**Output**: Interview notes, verbatim quotes, key insights
-
----
-
-### Empathy Mapping
-**Purpose**: Visual representation of what users Say, Think, Do, Feel
-
-```
-┌─────────────────────────────────────┐
-│            SAYS                     │
-│  "Actual quotes from user"          │
-├─────────────────────────────────────┤
-│            THINKS                   │
-│  What might they be thinking?       │
-├─────────────────────────────────────┤
-│            DOES                     │
-│  What actions did they take?        │
-├─────────────────────────────────────┤
-│            FEELS                    │
-│  What emotions surfaced?            │
-└─────────────────────────────────────┘
+```xml
+<methodologies>
+  <definition>Structured methods for requirements, analysis, problem-solving</definition>
+  
+  <categories>
+    <empathize>Understand users → See [empathize.md](empathize.md)</empathize>
+    <define>Frame problems → See [define.md](define.md)</define>
+    <ideate>Generate solutions → See [ideate.md](ideate.md)</ideate>
+    <diagnose>Find root causes → See [diagnose.md](diagnose.md)</diagnose>
+    <evaluate>Make decisions (Decision Matrix)</evaluate>
+  </categories>
+  
+  <by_agent>
+    <analyst>User Interviews, Empathy Mapping, Journey Mapping, Five Whys, Fishbone</analyst>
+    <pm>Problem Framing, HMW, POV Statement, JTBD, Brainstorming</pm>
+    <architect>Systems Thinking, Fishbone, Is/Is Not, Decision Matrix</architect>
+    <researcher>Five Whys, Systems Thinking, Is/Is Not</researcher>
+  </by_agent>
+  
+  <quick_reference>
+    <empathize>
+      <user_interviews>Deep conversations → See [empathize.md](empathize.md)</user_interviews>
+      <empathy_mapping>Says | Thinks | Does | Feels → See [empathize.md](empathize.md)</empathy_mapping>
+      <journey_mapping>Awareness → Action → Use → Support → See [empathize.md](empathize.md)</journey_mapping>
+    </empathize>
+    
+    <diagnose>
+      <five_whys>Ask "Why?" 5 times → See [diagnose.md](diagnose.md)</five_whys>
+      <fishbone>People | Process | Tech | Data | Env → See [diagnose.md](diagnose.md)</fishbone>
+      <is_is_not>Define boundaries → See [diagnose.md](diagnose.md)</is_is_not>
+      <systems_thinking>Feedback loops, leverage points → See [diagnose.md](diagnose.md)</systems_thinking>
+    </diagnose>
+    
+    <define>
+      <problem_framing>Transform observations into clear statements → See [define.md](define.md)</problem_framing>
+      <hmw>How might we [action] for [user] so that [outcome]? → See [define.md](define.md)</hmw>
+      <pov>[User] needs [what] because [insight] → See [define.md](define.md)</pov>
+      <jtbd>When [situation], I want [motivation], so I can [outcome] → See [define.md](define.md)</jtbd>
+      <affinity_clustering>Group observations to reveal patterns → See [define.md](define.md)</affinity_clustering>
+    </define>
+    
+    <ideate>
+      <brainstorming>Generate 50+ ideas without judgment → See [ideate.md](ideate.md)</brainstorming>
+      <scamper>7 lenses: Substitute, Combine, Adapt, Modify, Purposes, Eliminate, Reverse → See [ideate.md](ideate.md)</scamper>
+      <crazy_8s>8 sketches in 8 minutes → See [ideate.md](ideate.md)</crazy_8s>
+      <provotypes>Extreme prototypes to challenge assumptions → See [ideate.md](ideate.md)</provotypes>
+      <analogous_inspiration>Learn from other domains → See [ideate.md](ideate.md)</analogous_inspiration>
+    </ideate>
+    
+    <evaluate>
+      <decision_matrix>Criteria | Weight | Option A | Option B</decision_matrix>
+    </evaluate>
+  </quick_reference>
+  
+  <workflows>
+    <requirements>User Interviews → Empathy Map → Journey Map → Requirements</requirements>
+    <problem_definition>Five Whys → Fishbone → HMW → POV</problem_definition>
+    <solution_generation>Brainstorming → SCAMPER → JTBD</solution_generation>
+    <architecture>Systems Thinking → Is/Is Not → Decision Matrix → ADR</architecture>
+  </workflows>
+</methodologies>
 ```
 
 ---
 
-### Journey Mapping
-**Purpose**: Document complete user experience across touchpoints
-
-```
-Stage:      │ Awareness │ Consideration │ Action │ Use │ Support │
-────────────┼───────────┼───────────────┼────────┼─────┼─────────┤
-Actions     │           │               │        │     │         │
-Thoughts    │           │               │        │     │         │
-Emotions    │   😀      │      😐       │   😰   │ 😊  │   😡    │
-Pain Points │           │               │        │     │         │
-Opportunities│          │               │        │     │         │
-```
-
-**Prompts**:
-- What's their starting point?
-- What steps do they take?
-- Where do they struggle?
-- What delights them?
-- What's the emotional arc?
-
----
+## Detailed Guides
 
-## DEFINE Methods (Analyst, PM)
+**For understanding users:**
+- [empathize.md](empathize.md) - User Interviews, Empathy Mapping, Journey Mapping
 
-### Problem Framing
-**Purpose**: Transform observations into clear actionable problem statements
+**For framing problems:**
+- [define.md](define.md) - Problem Framing, HMW, POV, JTBD, Affinity Clustering
 
-**Prompts**:
-- What's the **real** problem? (not the symptom)
-- Who experiences this?
-- Why does it matter?
-- What would success look like?
+**For generating solutions:**
+- [ideate.md](ideate.md) - Brainstorming, SCAMPER, Crazy 8s, Provotypes, Analogous Inspiration
 
-**Output**: 1-2 sentence problem statement that inspires solutions
+**For finding root causes:**
+- [diagnose.md](diagnose.md) - Five Whys, Fishbone, Is/Is Not, Systems Thinking
 
 ---
 
-### How Might We (HMW)
-**Purpose**: Reframe problems as opportunity questions
-
-**Format**: `How might we [action] for [user] so that [outcome]?`
-
-**Examples**:
-- How might we help merchants update inventory faster?
-- How might we make checkout easier for mobile users?
-- How might we reduce friction in onboarding?
-
-**Rules**:
-- Opens solution space (not prescriptive)
-- User-centered
-- Implies positive change
+## Quick Examples
 
----
-
-### Point of View (POV) Statement
-**Purpose**: Specific user-centered problem statements
-
-**Template**:
+### Five Whys
 ```
-[User type] needs [what] because [insight]
+Problem: Users abandon checkout
+1. Why? → Too long
+2. Why? → Too many fields
+3. Why? → Unnecessary data
+4. Why? → No review process
+5. Why? → No validation process
+Root Cause: Missing validation process
 ```
 
-**Example**:
-> A busy merchant needs quick inventory updates because they lose sales when items show as available but are out of stock.
-
-**Prompts**:
-- What's driving this need?
-- Why does it matter to them?
-
----
-
-### Affinity Clustering
-**Purpose**: Group observations to reveal patterns and themes
-
-**Process**:
-1. Write each observation on a card/sticky
-2. Group similar items together (silently)
-3. Name each cluster
-4. Identify meta-themes
-
-**Prompts**:
-- What connects these?
-- What themes emerge?
-- What story do they tell?
-
----
-
-### Jobs to be Done (JTBD)
-**Purpose**: Identify what users are "hiring" solutions to accomplish
-
-**Template**:
+### Empathy Map
 ```
-When [situation], I want to [motivation], so I can [expected outcome]
+User: Busy merchant
+Says: "I don't have time"
+Thinks: "Too complicated"
+Does: Skips fields
+Feels: Frustrated 😤
+Insight: Values speed over completeness
 ```
 
-**Three Job Types**:
-| Type | Question |
-|------|----------|
-| **Functional** | What task are they completing? |
-| **Emotional** | How do they want to feel? |
-| **Social** | How do they want to be perceived? |
-
-**Prompts**:
-- What job are they trying to do?
-- What progress do they want?
-- What are they really hiring this for?
-- What alternatives exist?
-
----
-
-## IDEATE Methods (PM, Analyst)
-
-### Brainstorming Rules
-1. **No bad ideas** - defer judgment
-2. **Build on others** - "Yes, and..."
-3. **Aim for quantity** - 50+ ideas
-4. **Be visual** - sketch it
-5. **Stay on topic** - one problem at a time
-6. **Time-box** - 10-15 minutes max
-
----
-
-### SCAMPER
-**Purpose**: Apply 7 lenses to existing solutions for innovation
-
-| Letter | Question | Example |
-|--------|----------|---------|
-| **S**ubstitute | What can we substitute? | Different payment provider? |
-| **C**ombine | What can we combine? | Checkout + registration? |
-| **A**dapt | What can we adapt from elsewhere? | How does Uber handle this? |
-| **M**odify | How can we modify/magnify? | What if 10x faster? |
-| **P**ut to other uses | Other purposes? | Could this data serve analytics? |
-| **E**liminate | What can we remove? | Do we need this step? |
-| **R**everse | What if we reversed it? | User pulls instead of push? |
-
----
-
-## DIAGNOSIS Methods (Analyst, Architect, Researcher)
-
-### Five Whys Root Cause
-**Purpose**: Drill through symptoms to find root cause
-
-**Example**:
-```
-Problem: Users are abandoning checkout
-  └─ Why? → Payment fails frequently
-       └─ Why? → Timeout errors occur
-            └─ Why? → Payment gateway is slow
-                 └─ Why? → No connection pooling
-                      └─ Why? → Legacy implementation
-                           
-ROOT CAUSE: Legacy payment integration needs refactoring
-```
-
-**Tips**:
-- Don't stop at the comfortable answer
-- Look for systemic causes, not blame
-- May need 3-7 "whys" (5 is a guideline)
-
----
-
-### Fishbone Diagram (Ishikawa)
-**Purpose**: Map all potential causes across categories
-
-```
-                    ┌─────────────────────────────────────────┐
-    People ─────────┤                                         │
-                    │                                         │
-    Process ────────┤                                         │
-                    │              PROBLEM                    ├───▶ EFFECT
-    Technology ─────┤                                         │
-                    │                                         │
-    Data ───────────┤                                         │
-                    │                                         │
-    Environment ────┤                                         │
-                    └─────────────────────────────────────────┘
-```
-
-**Categories (adapt to context)**:
-| Category | Questions |
-|----------|-----------|
-| **People** | Skills? Training? Capacity? Communication? |
-| **Process** | Steps? Handoffs? Bottlenecks? Unclear? |
-| **Technology** | Systems? Tools? Integration? Performance? |
-| **Data** | Quality? Availability? Format? Timeliness? |
-| **Environment** | External factors? Dependencies? Constraints? |
-
----
-
-### Is/Is Not Analysis
-**Purpose**: Define problem boundaries by contrast
-
-| Question | IS | IS NOT |
-|----------|-----|--------|
-| **WHAT** is the problem? | | |
-| **WHERE** does it occur? | | |
-| **WHEN** does it happen? | | |
-| **WHO** experiences it? | | |
-| **HOW MUCH** impact? | | |
-
-**Prompts**:
-- Where does problem occur? Where doesn't it?
-- When does it happen? When doesn't it?
-- Who experiences it? Who doesn't?
-- What pattern emerges from the contrast?
-
----
-
-### Systems Thinking
-**Purpose**: Map interconnected elements, feedback loops, and leverage points
-
-**Components to Map**:
+### Journey Map
 ```
-┌─────────────┐     ┌─────────────┐     ┌─────────────┐
-│  ELEMENTS   │────▶│ CONNECTIONS │────▶│  FEEDBACK   │
-│             │     │             │     │   LOOPS     │
-│ What are    │     │ What        │     │ Reinforcing │
-│ the parts?  │     │ relationships?│   │ or balancing?│
-└─────────────┘     └─────────────┘     └─────────────┘
-                           │
-                           ▼
-                    ┌─────────────┐
-                    │  LEVERAGE   │
-                    │   POINTS    │
-                    │             │
-                    │ Where small │
-                    │ change = big│
-                    │ impact?     │
-                    └─────────────┘
+Awareness → Consideration → Action → Use → Support
+   😊          😐           😤       😰      😌
 ```
 
-**Prompts**:
-- What are the system components?
-- What relationships exist between them?
-- What feedback loops exist? (reinforcing or balancing)
-- What delays occur in the system?
-- Where are the leverage points?
-
----
-
-## EVALUATION Methods (Architect, PM)
-
-### Decision Matrix
-**Purpose**: Systematically evaluate options against weighted criteria
-
-**Template**:
-| Criterion | Weight | Option A | Option B | Option C |
-|-----------|--------|----------|----------|----------|
-| Performance | 3 | 8 (24) | 6 (18) | 9 (27) |
-| Cost | 2 | 7 (14) | 9 (18) | 5 (10) |
-| Complexity | 2 | 6 (12) | 8 (16) | 4 (8) |
-| Team Skills | 1 | 9 (9) | 5 (5) | 7 (7) |
-| **Total** | | **59** | **57** | **52** |
-
-**Process**:
-1. List options
-2. Define criteria (from NFRs, constraints)
-3. Assign weights (importance)
-4. Score each option (1-10)
-5. Calculate weighted scores
-6. Discuss and decide
-
----
-
-## RESEARCH Methods (Researcher)
-
-### Analogous Inspiration
-**Purpose**: Find solutions from different domains
-
-**Prompts**:
-- What other field solves a similar problem?
-- How does nature handle this? (biomimicry)
-- What's an analogous problem in another industry?
-- What can we borrow and adapt?
-
-**Examples**:
-| Problem | Analogous Domain | Insight |
-|---------|------------------|---------|
-| Queue management | Theme parks | FastPass reservation system |
-| Fraud detection | Immune system | Pattern recognition, antibodies |
-| Load balancing | Ant colonies | Distributed decision-making |
-
----
-
-## Quick Reference by Task
-
-### Requirements Gathering
-1. **User Interviews** → raw data
-2. **Empathy Mapping** → organize insights
-3. **Affinity Clustering** → find patterns
-4. **JTBD** → frame needs
-
-### Problem Definition
-1. **Problem Framing** → clear statement
-2. **Five Whys** → root cause
-3. **Is/Is Not** → boundaries
-4. **HMW** → opportunity questions
-
-### Solution Generation
-1. **Brainstorming** → quantity of ideas
-2. **SCAMPER** → systematic exploration
-3. **Analogous Inspiration** → cross-domain ideas
-
-### Architecture Decisions
-1. **Systems Thinking** → understand complexity
-2. **Fishbone** → cause analysis
-3. **Decision Matrix** → evaluate options
-
----
-
-## Method Selection Guide
-
-| Situation | Use These Methods |
-|-----------|-------------------|
-| Don't understand users | User Interviews, Empathy Mapping, Journey Mapping |
-| Problem is vague | Problem Framing, Five Whys, Is/Is Not |
-| Need root cause | Five Whys, Fishbone, Systems Thinking |
-| Need fresh ideas | Brainstorming, SCAMPER, Analogous Inspiration |
-| Organizing insights | Affinity Clustering, JTBD |
-| Comparing options | Decision Matrix |
-| Complex system issues | Systems Thinking, Fishbone |
+For full details and more examples, see the detailed guides above.