By lagz0ne
TBD -- JTBD-powered 5-tier UX methodology: Jobs To Be Done, Mini-Jobs, Ulwick Job Maps with emotional forces, Solution Epics/Stories, and traceability analysis.
A Claude Code plugin skill that runs a structured Jobs-to-be-Done analysis in 5 progressive tiers — from "why do users need this" to "what should we build" to "did we cover everything."
| Tier | Name | What Happens |
|---|---|---|
| 1 | JTBD | Extract job statements from a product description — solution-agnostic, motivation-first |
| 2 | Mini-Jobs | Decompose into sub-jobs with alternative paths (DAG structure, a-suffix convention) |
| 3 | Job Map | Map mini-jobs through Ulwick's 8 steps × 4 emotional forces (Push/Pull/Anxiety/Habit) → synthesized observations |
| 4 | Solution | Regroup by solution concern (not by JTBD) into Epics + Stories with emotional force tags and traceability |
| 5 | Traceability | 5 automated checks (coverage matrices, orphan detection, gap analysis framed as opportunities) |
Add to your Claude Code settings (.claude/settings.json):
{
"plugins": {
"marketplaces": [
"https://github.com/lagz0ne/tbd"
]
}
}
Or clone locally:
git clone https://github.com/lagz0ne/tbd.git
claude --plugin-dir ./tbd
/tbd # starts JTBD extraction (Tier 1)
"decompose the jobs" # Tier 2: mini-jobs
"map the jobs" # Tier 3: job map + emotional forces
"create epics and stories" # Tier 4: solution regrouping
"run traceability" # Tier 5: coverage + gap analysis
"resume" # auto-detect and continue from last tier
"full TBD" # run all tiers sequentially
"show example" # load golden example for calibration
The skill pauses at 2 hard checkpoints (after Tier 2 and Tier 3) for review before proceeding.
Included under skills/tbd/examples/golden-example/ — a complete 5-tier analysis of a Team Kanban Board:
.claude-plugin/
├── plugin.json
└── marketplace.json
skills/tbd/
├── SKILL.md # dispatch + workflow rules
├── references/
│ ├── tier1-jtbd.md # anti-patterns, procedure
│ ├── tier2-mini-jobs.md # 25% rule, DAG, checkpoint
│ ├── tier3-jobmap.md # emotional force layering, synthesis
│ ├── tier4-solution.md # regrouping, story format
│ └── tier5-traceability.md # 5A-5E verification
└── examples/golden-example/
├── 01-jtbd.md
├── 02-mini-jobs.md
├── 03-jobmap-observations.md
├── 04-solution.md
└── 05-traceability.md
MIT
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
No description provided.
No description provided.
Automated experiment loop for continuous improvement — bootstrap, benchmark, iterate, log
Adversarial triage with three roles: Pusher, Challenger, Arbiter. Produces high-confidence results through tension and refinement.
Rewrite-state reference for an explicit local control plane with traced-TDD failure ownership
npx claudepluginhub lagz0ne/tbd --plugin tbd-skillDiscovery & research skills: Discovery Interview Guide, Job Story Mapper, User Interview Synthesis, Assumption Mapper. Structure user research from screener to synthesis.
Comprehensive AI-assisted requirements elicitation. Supports stakeholder interviews (LLMREI pattern), document extraction, stakeholder simulation, domain research, gap analysis, user story mapping, customer journey mapping, JTBD analysis, prioritization (MoSCoW/Kano/WSJF), surveys, workshops, brainstorming, and business rules analysis. Exports to canonical, EARS, and Gherkin formats.
Pipeline PRD/GSD → JTBDs → User Stories validadas y priorizadas. 7 skills + 11 comandos. Source-agnostic (acepta PRD pegado, fichero o URL — sin acoplamiento a Notion/Jira). Incluye `/from-gsd` para integrar artefactos de Get Shit Done y `bridge/gsd-bridge.py` para mantener consistencia entre planning y ejecución.
ユーザーストーリーを可視化する専門スキル。6つの専門エージェントチームで、 ジャーニーマップの分析から Pencil (.pen) ビジュアル出力まで一気通貫で実行する。 プロダクト情報とターゲットユーザーを入力し、認知→検討→初回利用→習慣化→推薦の 5フェーズで行動・思考・感情・接点・機能・課題・機会・Devアクションを構造化し、 Markdownドキュメントと Pencil ビジュアルジャーニーマップを出力する。 離脱トリガー分析を強化し、ペインポイントと機会を視覚的に強調する。 ペルソナファイルがあれば自動読み込み、なければ手動入力でも動作する。 Use when: ジャーニーマップを可視化したい、ユーザー体験を図で表現したい、 カスタマージャーニーをビジュアル化したい、離脱要因を分析したい、 UXフローを .pen ファイルで出力したい。 Triggers: "ジャーニー", "journey", "ジャーニーマップ", "journey map", "ユーザー体験", "user journey", "UXフロー", "体験設計", "カスタマージャーニー", "customer journey", "可視化", "visualize", "user story", "ユーザーストーリー", "離脱分析", "drop-off" └── journey-map.pen <- Pencil ビジュアルジャーニーマップ - 名前(ラベル) - 年齢層 - 職業 - デジタルリテラシー(高/中/低) - 主な課題・目標
Business analysis toolkit: competitive analysis, UX strategy artifacts, market sizing, canvas, PRD, personas
Shape product direction through competitive analysis, design principles, experience mapping, and strategic alignment.