← ClaudeAtlas

user-need-essencelisted

Transform interviews, tickets, or feedback into the underlying user problems and requirements. Use when asked to understand user needs, pain points, or product requirements.
TeddyPika/Essence-Extract · ★ 0 · Data & Documents · score 72
Install: claude install-skill TeddyPika/Essence-Extract
# User Need Essence Extract the underlying user problems, needs, and requirements from the material provided. Focus on the pain points, motivations, constraints, and recurring signals in the evidence, without adding assumptions about users that the source does not support. ## Process 1. Identify the user group, context, and source of feedback or requirements being analyzed. 2. Extract recurring pain points, goals, friction, unmet needs, and stated constraints. 3. Separate direct user statements from inferred needs, and distinguish preferences from requirements. 4. Group similar themes into clear user problems and note any evidence of urgency, frequency, or severity. 5. Summarize the requirements implied by the material and any gaps where user evidence is incomplete. ## Response Use a concise format appropriate to the request: - **User need essence:** the central user problem or need in one or two sentences. - **Observed user problems:** the main pain points, frustrations, or unmet needs described. - **Needs and requirements:** the concrete requirements, goals, or behaviors implied by the user evidence. - **Context and constraints:** the conditions, constraints, or environments that matter. - **Uncertainty and gaps:** areas where the evidence is weak, ambiguous, or missing. Keep the summary evidence-based and avoid turning anecdotes into universal claims. ## Output contract By default, return a complete, self-contained HTML5 report, not bare JSON or Markdown. Use sema