jtbd-framerlisted

# JTBD Framer A feature idea in, the jobs behind it out — with the solution scrubbed from every statement, because a job that names the feature is just the feature wearing a costume. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Zero solution language:** no bracketed segment of any job statement contains the feature name or its mechanics, product/brand names, technology nouns (AI, app, button, dashboard, algorithm, integration), or UI verbs (click, tap, toggle, open). The check is a mechanical scan of every bracket against these classes. - **G2 — Canonical form:** every statement reads "When [situation], I want to [motivation], so I can [expected outcome]" — three brackets, each doing its own work (no outcome restated as motivation). - **G3 — Traceability:** every statement derives from the provided idea/context. No invented personas, segments, or circumstances that appear from nowhere. ## Steps 1. **Strip the idea to its actors and moment.** Who is the person, in what recurring situation, and what progress are they struggling to make? If the input has no who/when at all, ask one question — don't invent a persona. 2. **Ladder down from feature to job.** Ask "what does this feature let them stop doing / stop worrying about?" until the answer contains no technology. The feature is one candidate hire for the job, never the job. 3. **Draft 2–4 statements** in canonical form. Fewer, sharper jobs beat a laundry list — one feature rarely serve