{"id":53588,"plugin_id":"plugins_6ab368352eac819185c235df962b1b1c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:54:29.454Z","digest":"a8a4b7be1ddc49cbd07928f7ea53861e4e75c553331298efc3f7528d22c7500a","against":null,"payload":{"description":"Separate proposed features from customer problems and consolidate similar requests without losing important distinctions.","included_files":[],"name":"underlying-needs-and-request-deduplication","skill_md_contents":"---\nname: underlying-needs-and-request-deduplication\ndescription: Separate proposed features from customer problems and consolidate similar requests without losing important distinctions.\n---\n\n# Underlying Needs and Deduplication\n\nFor each entry capture (a) customer's stated request, (b) context/workflow, (c) problem or job-to-be-done explicitly described, and (d) inferred need, marked as inference. Identify missing evidence and suggest neutral follow-up questions. Do not assume the customer's proposed feature is the best solution.\n\nGroup requests only when their underlying need and relevant context align. Document merge rationale and keep the original statements traceable. Do not equate repeated comments from one customer with broad demand. When stable customer IDs are available, distinguish mentions, records, unique customers, and account-weighted counts; otherwise report only supported counts. Preserve conflicting viewpoints and rare high-severity blockers.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}