@mindrian_os/cli 1.13.0-beta.10 → 1.13.0-beta.43

package/references/meeting/summary-template.md

@@ -1,348 +0,0 @@
-# Meeting Summary Template -- Meeting Archive Package
-
-*Used by `file-meeting` to produce the complete meeting archive package.*
-
----
-
-## Meeting Archive Package
-
-Every filed meeting produces a self-contained archive folder with the following files:
-
-| File | Location | Purpose |
-|------|----------|---------|
-| Transcript | `room/meetings/YYYY-MM-DD-{name}/transcript.md` | Original transcript (preserved verbatim) |
-| Summary | `room/meetings/YYYY-MM-DD-{name}/summary.md` | Complete narrative + structured breakdown |
-| Speakers | `room/meetings/YYYY-MM-DD-{name}/speakers.md` | Who attended, roles, segment counts, profile links |
-| Decisions | `room/meetings/YYYY-MM-DD-{name}/decisions.md` | Extracted decisions with owners and impact sections |
-| Action Items | `room/meetings/YYYY-MM-DD-{name}/action-items.md` | Tasks with owners and deadlines (only if stated) |
-| Metadata | `room/meetings/YYYY-MM-DD-{name}/metadata.yaml` | Structured searchable metadata for cross-meeting lookup |
-| Audio | `room/meetings/YYYY-MM-DD-{name}/{filename}` | Audio copy (only if --audio input) |
-| Filed-to index | `room/meetings/YYYY-MM-DD-{name}/filed-to/` | Links to where each artifact was filed |
-| Compact reference | `room/meeting-YYYY-MM-DD-{name}.md` | Quick-access at room root |
-
-Each meeting folder is a complete knowledge artifact -- browsable, shareable, and self-contained.
-
----
-
-## Full Summary Template
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/summary.md`
-
-```markdown
----
-methodology: file-meeting
-type: meeting-summary
-meeting_date: {YYYY-MM-DD}
-meeting_name: {human-readable name}
-source: {transcript | velma}
-format_detected: {zoom | teams | otter | meet | raw | velma}
-duration_estimate: {minutes, if available}
-speakers:
-  - name: {speaker name}
-    role: {speaker role}
-    segments: {count}
-  - name: {speaker name}
-    role: {speaker role}
-    segments: {count}
-total_segments: {count}
-filed_segments: {count}
-skipped_segments: {count}
-flagged_noise: {count}
-rejected_segments: {count}
-created: {YYYY-MM-DD}
----
-
-# Meeting: {meeting_name}
-
-{Narrative lead paragraph in Larry's voice. 2-4 sentences summarizing what
-happened, what was decided, and what matters most. Written in third person
-with Larry's characteristic directness. NOT a bland summary -- Larry's
-personality comes through.}
-
-## Key Decisions
-
-{Numbered list of decisions made during the meeting. Each links to the
-filed artifact. If no decisions were made, state: "No explicit decisions
-were recorded in this meeting."}
-
-1. **{Decision summary}** -- {speaker} ({role})
-   Filed to: [[room/{section}/{artifact-name}.md]]
-
-## Insights Filed
-
-{Count} insights filed to {count} sections:
-
-- **{section}**: {count} insights
-  - {Brief insight summary} -- {speaker} ({role})
-  - {Brief insight summary} -- {speaker} ({role})
-- **{section}**: {count} insights
-  - {Brief insight summary} -- {speaker} ({role})
-
-## Contradictions Detected
-
-{List any contradictions found between segments in this meeting, or between
-meeting segments and existing room artifacts. If none: "No contradictions
-detected."}
-
-- **{Claim A}** ({speaker A}) vs **{Claim B}** ({speaker B})
-  Affects: [{sections}]
-  Status: Flagged for review
-
-## Gaps Identified
-
-{Questions raised during the meeting that represent knowledge gaps. These
-are filed as gap entries in their target sections.}
-
-- **{Gap description}** -- raised by {speaker} ({role})
-  Filed to: [[room/{section}/gaps/{artifact-name}.md]]
-
-## Action Items
-
-{Extracted action items with owners. NEVER invent deadlines that were not
-explicitly stated in the transcript.}
-
-| Owner | Task | Deadline | Context |
-|-------|------|----------|---------|
-| {name} | {task description} | {date or "not specified"} | {why this matters} |
-
-## Rejections
-
-{Segments the user rejected during confirm-then-file, with captured reasons.
-If none: "No segments were rejected."}
-
-| Segment | Suggested Section | Rejection Reason |
-|---------|-------------------|------------------|
-| {brief text} | {section} | {user's reason} |
-
-## Speakers
-
-{Count} speakers identified:
-
-| Speaker | Role | Segments | Key Contributions |
-|---------|------|----------|-------------------|
-| {name} | {role} | {count} | {1-sentence summary of their contributions} |
-
----
-
-*Filed by MindrianOS `file-meeting` on {created date}.*
-*Source: {source type} | Format: {format_detected}*
-```
-
----
-
-## Compact Reference Template
-
-**Location:** `room/meeting-YYYY-MM-DD-{name}.md`
-
-```markdown
----
-type: meeting-reference
-meeting_date: {YYYY-MM-DD}
-meeting_name: {name}
-full_summary: meetings/YYYY-MM-DD-{name}/summary.md
-speakers: {count}
-decisions: {count}
-insights: {count}
-actions: {count}
----
-
-# {meeting_name} ({YYYY-MM-DD})
-
-{One-paragraph summary -- same narrative lead from full summary.}
-
-**Decisions:** {count} | **Insights:** {count} | **Actions:** {count} | **Speakers:** {count}
-
-Full summary: [[meetings/YYYY-MM-DD-{name}/summary.md]]
-```
-
-This file lives at the root of the room directory for quick scanning. Users can `ls room/meeting-*.md` to see all meetings at a glance.
-
----
-
-## Transcript Storage Template
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/transcript.md`
-
-```markdown
----
-type: meeting-transcript
-meeting_date: {YYYY-MM-DD}
-meeting_name: {name}
-source: {transcript | velma}
-format_detected: {format}
-speakers: [{speaker names}]
-total_lines: {count}
----
-
-# Transcript: {meeting_name}
-
-{Original transcript preserved verbatim. No modifications.
-If Velma source, converted from JSON to readable format with
-timestamps and speaker labels.}
-```
-
-The transcript is stored EXACTLY as provided. No cleanup, no rewriting. The original is the source of truth. Larry's classifications and summaries are interpretations -- the transcript is evidence.
-
----
-
-## Filed-To Index Pattern
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/filed-to/`
-
-Each filed artifact gets a reference entry:
-
-```markdown
-# room/meetings/YYYY-MM-DD-{name}/filed-to/{NNN}-{section}.md
-
-Filed: [[room/{section}/{artifact-filename}.md]]
-Speaker: {name} ({role})
-Type: {segment_type}
-Confidence: {confidence}
-```
-
-Where `{NNN}` is a zero-padded sequence number matching the filing order (priority-ordered).
-
-This creates a bidirectional link: the artifact in the room section has `source: transcript` + `meeting_name` pointing back to the meeting, and the filed-to index points from the meeting to the artifact.
-
----
-
-## speakers.md Template
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/speakers.md`
-
-```markdown
----
-meeting_id: {YYYY-MM-DD-meeting-slug}
-meeting_date: {YYYY-MM-DD}
----
-# Speakers: {meeting_name}
-
-| Speaker | Role | Segments | Profile |
-|---------|------|----------|---------|
-| {name} | {role} | {count} | [[team/{role-plural}/{slug}/PROFILE.md]] |
-```
-
-One row per confirmed speaker. Profile links use the canonical slug from create-speaker-profile. Segment counts reflect the number of classified (non-noise) segments attributed to that speaker.
-
----
-
-## decisions.md Template
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/decisions.md`
-
-```markdown
----
-meeting_id: {YYYY-MM-DD-meeting-slug}
----
-# Decisions: {meeting_name}
-
-1. **{Decision summary}** -- {speaker} ({role})
-   Filed to: [[{section}/{artifact-filename}.md]]
-   Impact: {cascade_sections from the decision artifact}
-
-2. **{Decision summary}** -- {speaker} ({role})
-   Filed to: [[{section}/{artifact-filename}.md]]
-   Impact: {cascade_sections}
-```
-
-Extract from segments classified as `decision` in Step 3. Each entry links to the filed artifact and lists impact sections (cascade). If no decisions were made, write: "No explicit decisions were recorded in this meeting."
-
----
-
-## action-items.md Template
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/action-items.md`
-
-```markdown
----
-meeting_id: {YYYY-MM-DD-meeting-slug}
----
-# Action Items: {meeting_name}
-
-| Owner | Task | Deadline | Status |
-|-------|------|----------|--------|
-| {name} | {task description} | {date or "not specified"} | open |
-```
-
-Extract from segments classified as `action-item`. Deadlines ONLY if explicitly stated in transcript -- never invent deadlines. All items start as `status: open`. If no action items, write: "No action items were identified in this meeting."
-
----
-
-## metadata.yaml Template
-
-**Location:** `room/meetings/YYYY-MM-DD-{name}/metadata.yaml`
-
-```yaml
-meeting_id: {YYYY-MM-DD-meeting-slug}
-meeting_name: {human-readable meeting name}
-meeting_date: {YYYY-MM-DD}
-source: {transcript | velma}
-speakers:
-  - name: {full name}
-    role: {role}
-    slug: {speaker-slug matching profile directory}
-topics:
-  - {dominant topic 1}
-  - {dominant topic 2}
-decisions_count: {N}
-insights_count: {N}
-action_items_count: {N}
-sections_touched:
-  - {section-name}
-  - {section-name}
-has_audio: {true | false}
-```
-
-Created LAST in the archive after all other files are written (counts depend on completed processing). Topics are inferred from dominant themes of filed segments. Speaker slugs MUST match directory names from create-speaker-profile.
-
-### Searchability
-
-metadata.yaml is designed for grep-based cross-meeting lookups without indexing:
-
-- **Find meetings by speaker:** `grep -rl '{speaker-slug}' room/meetings/*/metadata.yaml`
-- **Find meetings by topic:** `grep -rl '{topic}' room/meetings/*/metadata.yaml`
-- **Find meetings with decisions:** `grep -l 'decisions_count: [1-9]' room/meetings/*/metadata.yaml`
-- **Find meetings by date range:** Scan `meeting_date` fields across metadata.yaml files
-
-This enables Larry to answer questions like "What did Lawrence say about pricing?" or "Which meetings had action items?" by scanning metadata.yaml files directly.
-
----
-
-## Summary Sections -- Required vs Optional
-
-| Section | Required | When to Include |
-|---------|----------|-----------------|
-| Key Decisions | YES | Always -- state "none recorded" if empty |
-| Insights Filed | YES | Always -- show counts by section |
-| Contradictions Detected | YES | Always -- state "none detected" if empty |
-| Gaps Identified | YES | Always -- state "none identified" if empty |
-| Action Items | YES | Always -- state "no action items" if empty |
-| Rejections | YES | Always -- state "none rejected" if empty |
-| Speakers | YES | Always -- list all identified speakers |
-
-Every section is always present. This makes the summary format consistent and machine-parseable. Empty sections explicitly state their emptiness rather than being omitted.
-
----
-
-## Meeting Name Convention
-
-The `{name}` in paths is derived from the meeting name:
-
-1. Lowercase
-2. Replace spaces with hyphens
-3. Remove special characters
-4. Truncate to 50 characters
-
-Examples:
-- "Board Strategy Session Q1" -> `board-strategy-session-q1`
-- "Mentor Check-in with Lawrence" -> `mentor-check-in-with-lawrence`
-- "Investor Due Diligence Call" -> `investor-due-diligence-call`
-
----
-
-## Cross-Reference
-
-- Artifact format: `references/meeting/artifact-template.md`
-- Segment classification: `references/meeting/segment-classification.md`
-- Speaker profiles: `references/meeting/speaker-profile-template.md`
-- Section routing: `references/meeting/section-mapping.md`

package/references/meeting/transcript-patterns.md

@@ -1,226 +0,0 @@
-# Transcript Format Patterns -- Speaker Identification Reference
-
-*Used by `file-meeting` to detect transcript format and extract speaker turns.*
-
----
-
-## Format Detection Order
-
-Larry tries each format in order. First match wins. If no format matches, treat as **Raw Paste**.
-
-| Priority | Format | Detection Pattern | Confidence |
-|----------|--------|-------------------|------------|
-| 1 | Velma JSON | Valid JSON with `speaker_id` field | HIGH |
-| 2 | Zoom | Lines matching `HH:MM:SS Speaker Name: text` | HIGH |
-| 3 | Teams | Lines matching `[HH:MM:SS] Speaker Name` or `Speaker Name HH:MM:SS` | HIGH |
-| 4 | Otter.ai | Lines matching `Speaker Name  HH:MM` (double-space) | MEDIUM |
-| 5 | Google Meet | Lines matching `Speaker Name HH:MM:SS` (no colon after name) | MEDIUM |
-| 6 | Raw Paste | No timestamps, no speaker labels detected | LOW |
-
----
-
-## Zoom Format
-
-**Pattern:** `HH:MM:SS Speaker Name: text`
-
-```
-00:02:15 Sarah Chen: I think we should focus on the enterprise segment first.
-00:02:45 David Park: Agreed. The SMB numbers don't support the unit economics yet.
-```
-
-**Regex:**
-```
-^(\d{2}:\d{2}:\d{2})\s+([^:]+?):\s+(.+)$
-```
-
-- Group 1: Timestamp (`HH:MM:SS`)
-- Group 2: Speaker name (trimmed)
-- Group 3: Spoken text
-
-**Edge cases:**
-- Speaker names may contain spaces ("Sarah Chen")
-- Colons in speech text are captured in Group 3 (greedy after first `:`)
-- Some Zoom exports omit seconds: `00:02 Speaker Name: text` -- use fallback regex `^(\d{2}:\d{2}(?::\d{2})?)\s+([^:]+?):\s+(.+)$`
-
----
-
-## Microsoft Teams Format
-
-**Pattern A:** `[HH:MM:SS] Speaker Name`
-**Pattern B:** `Speaker Name HH:MM:SS`
-
-```
-[00:02:15] Sarah Chen
-I think we should focus on the enterprise segment first.
-
-[00:02:45] David Park
-Agreed. The SMB numbers don't support the unit economics yet.
-```
-
-Or:
-
-```
-Sarah Chen 00:02:15
-I think we should focus on the enterprise segment first.
-
-David Park 00:02:45
-Agreed. The SMB numbers don't support the unit economics yet.
-```
-
-**Regex (Pattern A):**
-```
-^\[(\d{2}:\d{2}:\d{2})\]\s+(.+)$
-```
-
-**Regex (Pattern B):**
-```
-^(.+?)\s+(\d{2}:\d{2}:\d{2})$
-```
-
-- Teams format separates the speaker line from the text line
-- Text follows on the next line(s) until the next speaker marker
-- Blank lines often separate speaker turns
-
----
-
-## Otter.ai Format
-
-**Pattern:** `Speaker Name  HH:MM` (double-space separator)
-
-```
-Sarah Chen  0:02
-I think we should focus on the enterprise segment first.
-
-David Park  0:02
-Agreed. The SMB numbers don't support the unit economics yet.
-```
-
-**Regex:**
-```
-^(.+?)\s{2,}(\d+:\d{2})$
-```
-
-- Group 1: Speaker name
-- Group 2: Timestamp (`M:SS` or `MM:SS` -- Otter uses minutes, not hours)
-- Double-space (2+) separates name from timestamp
-- Text follows on subsequent lines until next speaker marker
-
-**Edge cases:**
-- Otter sometimes labels unknown speakers as "Speaker 1", "Speaker 2"
-- Timestamps are minutes:seconds, not hours:minutes:seconds
-
----
-
-## Google Meet Format
-
-**Pattern:** `Speaker Name HH:MM:SS`
-
-```
-Sarah Chen 00:02:15
-I think we should focus on the enterprise segment first.
-
-David Park 00:02:45
-Agreed. The SMB numbers don't support the unit economics yet.
-```
-
-**Regex:**
-```
-^(.+?)\s+(\d{2}:\d{2}:\d{2})$
-```
-
-- Similar to Teams Pattern B but Google Meet always uses `HH:MM:SS`
-- Disambiguation from Teams: check if ALL timestamps have HH:MM:SS format (Meet) vs mixed (Teams)
-
-**Disambiguation rule:** If the transcript has `[` brackets around timestamps, it is Teams. If no brackets and timestamps are at end of line, check consistency -- Meet uses `HH:MM:SS` uniformly.
-
----
-
-## Raw Paste (No Labels)
-
-**Detection:** No lines match any of the above patterns in the first 20 lines.
-
-```
-I think we should focus on the enterprise segment first.
-Agreed. The SMB numbers don't support the unit economics yet.
-What about the partnership with Acme Corp?
-That fell through last week. We need a new distribution strategy.
-```
-
-**Handling:**
-1. Larry CANNOT reliably identify speakers from raw text alone
-2. **Ask the user:** "I don't see speaker labels in this transcript. Can you tell me who was in the meeting? I'll do my best to attribute statements."
-3. If user provides speaker list, Larry uses contextual clues (first person references, expertise signals, role language) to attribute -- with LOW confidence on all attributions
-4. All segments from raw paste get `confidence: 0.3` maximum unless user confirms attribution
-
----
-
-## Velma Output (JSON)
-
-**Detection:** File is valid JSON with `speaker_id` field in entries.
-
-```json
-{
-  "meeting_id": "mtg_abc123",
-  "duration_seconds": 3600,
-  "segments": [
-    {
-      "speaker_id": "spk_001",
-      "speaker_name": "Sarah Chen",
-      "text": "I think we should focus on the enterprise segment first.",
-      "start_time": 135.2,
-      "end_time": 141.8,
-      "emotions": ["confident", "analytical"],
-      "confidence": 0.94
-    },
-    {
-      "speaker_id": "spk_002",
-      "speaker_name": "David Park",
-      "text": "Agreed. The SMB numbers don't support the unit economics yet.",
-      "start_time": 165.0,
-      "end_time": 172.3,
-      "emotions": ["agreement", "concern"],
-      "confidence": 0.91
-    }
-  ]
-}
-```
-
-**Schema:**
-- `speaker_id`: Velma's internal speaker identifier (stable across the meeting)
-- `speaker_name`: Resolved name (may be "Unknown Speaker 1" if Velma can't identify)
-- `text`: Transcribed speech
-- `start_time` / `end_time`: Seconds from meeting start (float)
-- `emotions[]`: Velma's emotion detection (20+ categories)
-- `confidence`: Velma's transcription confidence (0.0-1.0)
-
-**Advantages over text formats:**
-- Pre-segmented speaker turns (no regex needed)
-- Emotion metadata enriches segment classification
-- High confidence scores from Velma's diarization
-- `source: velma` in artifact frontmatter (vs `source: transcript`)
-
----
-
-## Ambiguity Resolution
-
-When Larry cannot determine the format:
-
-1. **Count pattern matches** across the first 20 lines for each format regex
-2. **Highest match count wins** -- format with most matching lines
-3. **Tie-breaking:** Prefer more specific formats (Zoom > Meet > Teams > Otter > Raw)
-4. **If still ambiguous:** Ask the user: "This looks like it could be [Format A] or [Format B]. Which tool recorded this meeting?"
-5. **Log the detection** in meeting summary: `format_detected: zoom` (or whichever)
-
----
-
-## Speaker Name Normalization
-
-After extraction, normalize speaker names:
-
-1. **Trim whitespace** from both ends
-2. **Collapse internal whitespace** to single spaces
-3. **Title case** if all-caps or all-lowercase input
-4. **Deduplicate:** "Sarah Chen" and "Sarah" in the same meeting likely refer to the same person -- ask user to confirm
-5. **Map to existing profiles:** Check `room/team/` for existing speaker profiles by name match
-
-Speaker names become folder names in `room/team/{role-plural}/{firstname-lastname}/` -- keep them filesystem-safe (lowercase, hyphens, no special characters).

package/references/methodology/analyze-needs.md

@@ -1,135 +0,0 @@
-# Jobs To Be Done -- Framework Reference
-
-*Loaded on demand by `/mos:analyze-needs`*
-
-## Framework Overview
-
-Jobs To Be Done discovers what progress customers are really trying to make. Customers do not buy products -- they hire them. And they fire them when something better shows up. The opportunity lives in the struggling moment: the instant someone realizes the old way is not working anymore. Based on Clayton Christensen's JTBD framework, applied through Larry's customer-need-finder teaching style.
-
-The framework applies beyond product markets: a graduate student's "job" is producing original research that advances their field. A career-pivoter's "job" is translating existing expertise into a new professional identity. Frame the analysis around whatever domain the user is exploring.
-
-The operating principle: focus on outcomes, not features. Opportunity lives in unmet progress. Most companies obsess over features -- the easy part. The hard part is the struggling moment. That is where innovation begins.
-
-## The Voice (This Methodology)
-
-Larry in customer-need-finder mode. Conversational, provocative, concise. Warm but demanding. Your job is to pull the real job out of them -- they will start with features and you must redirect to progress.
-
-Signature phrases:
-- "People don't want a quarter-inch drill. They want a quarter-inch hole. But actually -- they want the shelf hung."
-- "Very simply... customers don't buy products. They hire them."
-- "Here's what everyone misses: the future doesn't arrive incrementally."
-- "That's not a problem -- that's a category."
-- "You've given me the product. What's the job it's hired to do?"
-- "That's the functional job. What's the emotional job underneath it?"
-- "The struggling moment is where innovation lives."
-
-Anti-patterns to catch:
-- Accepting features as jobs -- "They want a faster dashboard" is not a job. "They need to make a confident decision in under 30 seconds" is a job.
-- Skipping emotional and social dimensions -- if you only have the functional job, you are halfway there
-- Forgetting "do nothing" as a competitor -- the biggest competitor is often inaction
-- Confusing buyer with user -- who decides? Who pays? Who suffers?
-- Staying abstract -- "Describe the last time this happened. What did they do? What did they feel?"
-- Listing all phases upfront -- walk them through, one question at a time
-- Never teach the framework abstractly -- apply it to their actual situation
-
-## Phases
-
-### Phase 1: Customer Identification (turns 1-3)
-
-ONE question at a time. Do not rush.
-
-1. "Who is your customer? Not the segment -- a real person. Describe them."
-2. "What are they trying to accomplish? Not what they want to buy -- what progress are they making?"
-3. "When did they first realize the old way wasn't working?"
-
-### Phase 2: Job Statement (turns 3-5)
-
-4. Break the job into steps: Define, Locate, Prepare, Execute, Monitor, Modify, Conclude.
-5. For each step: "What does success look like here? What makes it hard?"
-6. Craft the job statement: "When {situation}, I want to {motivation}, so I can {outcome}."
-
-### Phase 3: Importance vs. Satisfaction Scoring (turns 5-7)
-
-7. For each job step, rate:
-   - How important is getting this right? (1-10)
-   - How satisfied are they with current solutions? (1-10)
-8. **Opportunity = High Importance + Low Satisfaction.** That is the gap.
-
-### Phase 4: Blocked Steps Analysis (turns 7-9)
-
-9. "Which steps have the widest gap between importance and satisfaction?"
-10. "What's blocking progress? Is it functional, emotional, or social?"
-    - **Functional**: The practical task will not complete
-    - **Emotional**: They feel frustrated, anxious, incompetent
-    - **Social**: They look bad, feel judged, cannot explain the choice
-11. "That's not a problem -- that's a category. What specific moment makes them give up?"
-
-### Phase 5: Opportunity Mapping (turns 9+)
-
-12. Cluster the blocked steps into opportunity spaces.
-13. For each: "Who else has this job? How big is this?"
-14. Identify highest-leverage opportunities where functional, emotional, and social jobs align.
-
-## Artifact Template
-
-```markdown
----
-methodology: analyze-needs
-created: {date}
-depth: {quick|deep}
-problem_type: {type}
-venture_stage: {stage}
-room_section: market-analysis
----
-
-# Jobs To Be Done -- {Topic}
-
-## Customer
-{Specific person description -- not a segment}
-
-## Job Statement
-When {situation}, I want to {motivation}, so I can {outcome}.
-
-## Job Steps
-
-| Step | Description | Importance (1-10) | Satisfaction (1-10) | Gap |
-|------|-------------|-------------------|---------------------|-----|
-| Define | {what they do} | {n} | {n} | {importance - satisfaction} |
-| Locate | {what they do} | {n} | {n} | {gap} |
-| Prepare | {what they do} | {n} | {n} | {gap} |
-| Execute | {what they do} | {n} | {n} | {gap} |
-| Monitor | {what they do} | {n} | {n} | {gap} |
-| Modify | {what they do} | {n} | {n} | {gap} |
-| Conclude | {what they do} | {n} | {n} | {gap} |
-
-## Blocked Steps
-
-| Step | Blocker Type | Specific Moment | Current Workaround |
-|------|-------------|-----------------|-------------------|
-| {step} | Functional / Emotional / Social | {the moment they give up} | {what they do instead} |
-
-## Opportunity Clusters
-
-| Cluster | Blocked Steps | Job Dimensions | Size Estimate |
-|---------|--------------|----------------|---------------|
-| {name} | {steps} | Functional + Emotional + Social | {who else has this job} |
-
-## Homework
-Interview one real customer this week. Don't ask what they want -- ask what they were trying to accomplish the last time they used your product. Record the struggling moment. Bring it back.
-```
-
-## Default Room
-
-market-analysis
-
-## Cross-References
-
-- **explore-domains**: If JTBD analysis reveals a new domain territory
-- **validate**: If opportunity clusters need evidence validation
-- **lean-canvas**: If JTBD insights feed into a business model
-- **find-bottlenecks**: If blocked steps point to system-level constraints
-
-## Quick Pass vs Deep Dive
-
-- **Quick (10-15 min)**: Customer + job statement + top 3 blocked steps. Good when user already understands their customer and needs to articulate the job.
-- **Deep (30-45 min)**: Full five-phase arc, complete job steps mapping, importance/satisfaction scoring, opportunity clustering. Best for early-stage ventures where the customer need is not yet validated.