dbs-jtbd
dontbesilent JTBD Job Clarification. Uses the Jobs to Be Done framework to identify the progress users want to make in specific contexts, the forces driving solution switching, and observable choice criteria—optimizing products, content, services, decisions, and AI prompts accordingly. Invocation command: /dbs-jtbd. Use when users ask "What problem are we actually solving?", "Why choose this solution?", or "Rewrite this prompt using JTBD".
1How It Works & Mechanism
Pure prompt orchestration with zero scripts or external dependencies: All capabilities derive from the judgment framework, questioning discipline, and output templates in SKILL.md
本 Skill 从 Jobs to Be Done 视角理解用户要完成的事,用于产品、内容、决策或 AI 协作中的任务澄清。
Core mechanism is "Progress first, solution second": Demotes user-requested deliverables (writing articles, creating courses, building agents) to candidate means, then reverse-engineers the progress they want to make
用户说「帮我写一篇文章」「我需要一个课程」「给我做一个 Agent」时,先不要把这句话直接当成需求结论。它通常只说明了用户想到的方案。
Job statements are enforced into fillable syntactic templates requiring "progress written as change, outcomes grounded in perceptible states", filtering out vague adjectives from the output
当我处于 `{情境}`,我想要 `{推进的进展}`,以便 `{得到的结果}`。
Uses JTBD's three-layer jobs and the "Four Forces of Progress" (Push, Pull, Anxiety, Habit) as a fixed checklist, requiring recommendations to address all four forces rather than merely magnifying selling points
一个方案被采用,通常需要推力和拉力强过焦虑与习惯。输出建议时要处理这四种力量,不能只放大卖点。
"Minimal questioning" discipline: First drafts job hypotheses based on existing materials, asking at most 1 concrete factual question only when missing information would change recommendations, while forbidding broad, open-ended questions
只有以下信息缺失且会改变建议时,才问 1 个最小问题:
Choice criteria must be "observable, evaluable, and prioritized": Categorized into Must-haves / Value-adds / Acceptable trade-offs, requiring phrases like "simple and easy to use" to be unpacked into verifiable statements
标准要可观察。把「简单好用」还原为「第一次使用 10 分钟内能否得到可修改的结果」这类表述。
Outputs are routed by scenario: AI collaboration → rewritten prompt; Product or service → job definition and switching anxiety mitigation; Content sales → context and credible proof; Personal decisions → minimum viable verification action
| 产品或服务 | 任务定义、雇用时刻、需求优先级、降低切换焦虑的设计 |
Built-in prompt skeleton for AI collaboration that front-loads the job statement and complements context, materials, boundaries, deliverables, and acceptance criteria—enabling models to derive solutions from constraints
把任务陈述放在提示词开头,并补上情境、已有材料、边界、交付物和验收标准。
2Core Capabilities
4Recommended Governance & Evidence
- SKILL.md: Pure prompt instructions and rule text, without script execution or external side effects
5Second-Pass Verification
- [ok] 外部资源/工具:是否存在 SKILL.md 未声明的依赖 — 目录内仅 SKILL.md 与 agents/openai.yaml;token 扫描无 URL/CLI/API/包名命中,external_deps 为空数组成立。agents/openai.yaml 只含 display_name/short_description/default_prompt 三个界面字段,非运行依赖。
- [ok] 安全结论:是否真的零文件读写 — 全文无读取或写入指令——不要求读用户文件、不要求落盘产物(唯一「输出」是对话中的 markdown 模板)。相比同批 dbs-save/dbs-report/dbs-knowledge 有明确落盘动作,本 skill 属同批风险最低档。
- [ok] 实现原理是否成立:宣称的「切换力量」与「可观察标准」是否真有可执行定义 — 四力表给出每力的具体提问句(如「旧做法造成了什么具体损失、压力或阻塞?」),选择标准要求三分类并标优先级、给出「简单好用→第一次使用 10 分钟内能否得到可修改的结果」的还原示例。非口号式条目。
- [unlocatable] 证据定位:star/last_push 等仓库级元数据 — stars 与 last_push 来自站点池 data/pool.json 的 GitHub API 采集值,pin 源码内无此数据,无法在仓库文件内逐字命中;license 可在仓库根 LICENSE 逐字命中。
6Verdict & Scenarios
236334174ad98f29…