القائمة
Drafts a JTBD-native product brief from Job Map data. Accepts a Job Map YAML file (.jtbd/jobs/*.yml). Outputs to .jtbd/briefs/. Use when: "product brief", "jtbd brief", "write prd".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generates an HTML diagram of the four forces driving a switch. Accepts either a single interview file (.jtbd/switches/*.yml) or an aggregate patterns file (.jtbd/patterns/*.yml). Outputs a standalone HTML file to .jtbd/forces/. Use when: "draw forces", "jtbd forces", "forces diagram".
Run the full JTBD analysis pipeline on a batch of interview transcripts. Analyzes each transcript into a Switch analysis, then finds cross-interview patterns. Accepts a directory of transcript files or Fireflies meeting IDs. Use when: "analyze all interviews", "jtbd pipeline", "batch analysis", "process transcripts".
Guided walkthrough of the JTBD skills. Takes a new user from "what is this?" to "I understand the four forces and know what to do next" in about 5 minutes. Uses existing example data, no real interview required. Use when: "demo", "tutorial", "how does this work", "show me", "getting started".
Generate a customized Switch interview script based on your product context and existing evidence gaps. Outputs a ready-to-use markdown guide with Moesta's timeline reconstruction questions and force-probing techniques. Use when: "interview script", "jtbd interview", "interview guide", "how to interview".
Find cross-interview patterns across 3+ switch analyses in .jtbd/switches/. Clusters recurring jobs, identifies force patterns, surfaces evidence gaps, and generates actionable recommendations. Outputs structured YAML to .jtbd/patterns/. Use when: "find patterns", "jtbd patterns", "cross-interview", "what are the jobs".
Analyze a customer interview transcript using Moesta's Switch methodology. Extracts the switching timeline, four forces (push/pull/anxiety/habit), and a Klement-format job story. Outputs structured YAML to .jtbd/switches/. Use when: "analyze interview", "jtbd switch", "customer interview", "switching analysis".
| name | jtbd-brief |
| version | 1.0.0 |
| description | Drafts a JTBD-native product brief from Job Map data. Accepts a Job Map YAML file (.jtbd/jobs/*.yml). Outputs to .jtbd/briefs/. Use when: "product brief", "jtbd brief", "write prd". |
| allowed-tools | ["Bash","Read","Write","AskUserQuestion"] |
Check for .jtbd/ directory.
Make sure the .jtbd/briefs/ directory exists.
[ -d ".jtbd/jobs" ] || { echo "Error: .jtbd/jobs/ directory not found. Run /jtbd-map first."; exit 1; }
mkdir -p .jtbd/briefs/
.jtbd/jobs/).Use the Read tool to read the Job Map file. Ask the user if they also want to include context from a specific pattern file; if yes, read that too.
Instruct the LLM to draft a "JTBD-Native" Product Brief. The brief must explicitly link proposed features or interventions back to the friction points identified in the Job Map.
Structure the brief exactly like this:
# Product Brief: [Feature/Project Name]
## 1. The Job
[What the customer is trying to achieve]
## 2. The Forces
[What is pushing/pulling them, and what anxieties/habits must be overcome]
## 3. Timeline Interventions
[Where in the customer's journey the product should intercept them]
## 4. Map Opportunities
[Specific feature proposals directly linked to the friction points in the Job Map]
Write the generated Markdown to .jtbd/briefs/[feature-slug].md using the Write tool.
Inform the user where the file was saved.