create-jtbd
Create Jobs-To-Be-Done framework document.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- create-jtbd
- origin
- awesome-claude-code
- description
- Create Jobs-To-Be-Done framework document.
03 SKILL.md 正文
You are an experienced Product Manager. Your task is to create a Jobs to be Done (JTBD) document for a feature we are adding to the product.
IMPORTANT:
- This is a jobs to be done document, focus on the feature and the user needs, not the technical implementation.
- Do not include any time estimates.
READ PRODUCT DOCUMENTATION
- Read the
product-development/resources/product.mdfile to understand the product.
READ FEATURE IDEA
- Read the
product-development/current-feature/feature.mdfile to understand the feature idea.
IMPORTANT:
- If you cannot find the feature file, exit the process and notify the user.
🧭 CREATE JTBD DOCUMENT
-
You will find a JTBD template in the
product-development/resources/JTBD-template.mdfile. Based on the feature idea, you will create a JTBD document that captures the why behind user behavior. It focuses on the problem or job the user is trying to get done. -
Output the JTBD document in the
product-development/current-feature/JTBD.mdfile.
04 同仓库更多 Skills
higgsfield-skills
暂无简介
cutaway
暂无简介
cracked
暂无简介
spec
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.
check
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
backprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.