jtbd
Jobs to Be Done Analysis
Analyze a product, feature, or situation through the Jobs to Be Done framework to understand what customers really want.
Instructions
Identify the underlying jobs customers are trying to accomplish, including functional, emotional, and social dimensions. Consider the full context of when and why they "hire" solutions.
Output Format
Subject: [Product/feature/situation being analyzed]
The Context
When does the job arise? [Describe the triggering situation or circumstance]
More from neurofoo/agent-skills
socratic
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
121feynman
Feynman Technique for deep learning—explain a concept simply, identify gaps, fill them, then refine. Use when learning something new, testing understanding, or preparing to teach.
117scamper
SCAMPER creative brainstorming with seven prompts—Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse. Use for innovation, product ideas, or breaking creative blocks.
655whys
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
51ooda
OODA loop decision framework (Observe, Orient, Decide, Act). Use for complex decisions, problem-solving, unclear situations, or when someone is jumping to solutions without analysis.
50redteam
Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect.
50