Jtbd Analyzer

Uncover the real "job" customers hire your product to do. Goes beyond features to understand functional, emotional, and social motivations. Use when user say...

Security Scan

The skill is an instruction-only Jobs‑To‑Be‑Done analysis helper whose content, files, and requirements are consistent with its stated purpose and it does not request extra privileges or credentials.

Purpose & Capability

Name, description, and provided materials focus on JTBD analysis. There are no unrelated environment variables, binaries, or install steps; the examples and framework files match the stated purpose.

Instruction Scope

SKILL.md contains interview prompts, a job-statement process, output templates, and integration suggestions. It does not instruct the agent to read arbitrary files, access environment variables, or send data to external endpoints beyond normal skill output.

Install Mechanism

This is an instruction-only skill with no install spec and no code files to execute. That minimizes filesystem/remote-install risk.

Credentials

The skill declares no required environment variables, credentials, or config paths. The runtime instructions do not reference secrets or other unrelated credentials.

Persistence & Privilege

always is false and default autonomous invocation is expected. The skill does not request persistent system presence, nor does it attempt to modify other skills or system configuration.

Assessment

This skill is coherent and low-risk: it only provides interview prompts, templates, and analysis guidance. Before using, avoid pasting sensitive personal data or secrets into prompts. Note the SKILL.md references other skills (first-principles-decomposer, cross-pollination-engine, etc.); review those skills separately if you plan to chain them, since they may request additional permissions or credentials. If you want extra caution, test the skill with non-sensitive example products first.

Jobs-To-Be-Done Analyzer

The Core Concept

Customers don't buy products. They HIRE products to do a job.

"People don't want a quarter-inch drill. They want a quarter-inch hole." Actually: They want a shelf → to display photos → to feel proud of family.

The Three Job Dimensions

Dimension	Question	Format
Functional	What task needs doing?	"Help me [verb] [object]"
Emotional	How do I want to feel?	"Make me feel [emotion]"
Social	How do I want to be seen?	"Help me be seen as [quality]"

The Process

1. Job Statement: "When [situation], I want to [motivation], so I can [outcome]"
2. Map all 3 dimensions for each user type
3. Find real competition: What ELSE could do this job?
4. Prioritize: Which jobs are most critical and underserved?

Output Format

PRODUCT: [What you're analyzing]

For [User Type]:
JOB: "When [situation], I want [motivation], so I can [outcome]"

📋 FUNCTIONAL: [Task to accomplish]
💜 EMOTIONAL: [Feeling desired]
👥 SOCIAL: [Perception desired]

ALTERNATIVES: [What else could do this job?]
UNDERSERVED: [What part isn't done well?]
PRIORITY: Critical / Important / Nice-to-have

Key Questions

1. "What were you trying to accomplish when you [action]?"
2. "Walk me through the last time you needed to [job]"
3. "What would you do if [product] didn't exist?"
4. "What's frustrating about how you currently [job]?"

Integration

Compounds with:

• first-principles-decomposer → Decompose job to atomic need
• cross-pollination-engine → Find how others solve similar jobs
• app-planning-skill → Use JTBD to inform features

---

See references/examples.md for Artem-specific JTBD analyses