Explore skills

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".

Merge current PR after CI passes. Waits for all checks, squash merges, deletes branch, switches to main.

Delegates knowledge bank lookups to Explore subagents with reflections-first strategy that learns from past mistakes. Checks /reflections/ directory before documentation to extract documented failures to avoid and proven approaches to apply. Automatically triggers when user mentions services ([project-a], [project-b], [project-c], Claude Code), requests investigations, or queries past lessons. Ret

Tool-tier guidance for symbol search and call/reference tracing. Preloaded into agents that locate code; not user-facing.

Run code review with dynamic agent scaling (3-13 agents based on change size)

Use when the user asks to improve, structure, or templatize a prompt before execution by Codex or another AI agent.

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".

Jobs to Be Done skills for Claude Code. Turn customer interview transcripts into structured, version-controlled demand evidence.

Tool-tier guidance for codebase exploration and architecture overview. Preloaded into agents that explore code structure; not user-facing.

Create Architecture Decision Records (ADRs) based on MADR template. Use when the user asks to "create an ADR", "document a decision", "write an ADR", or provides decision context that needs to be formalized.

Initialize .bdk/settings.json for this project. Run once per project when BDK blocks session start with missing settings.