What problem does it solve? Teams often jump straight to building a dashboard, agent, or automation without checking whether an existing tool already solves the problem. This Skill turns recurring friction or unmet needs into a structured opportunity map that decides whether to build, buy, complement, or wait before any code is written. ## Core Features & Use Cases - Signal Normalization and Classification: Converts raw ideas and weak signals (like "build a dashboard") into observable, repeated pain points, then classifies each against existing tools, thin complements, and first useful versions. - Single Candidate Recommendation: Ranks classified signals by repetition, data sources combined, manual pain, and testability to recommend at most one candidate worth a first build. - Data Risk Assessment: Flags whether the first version can run on mock, local, or read-only data versus real company or customer data requiring access control. - Use Case: A team lead notices engineers manually check which PRs block each release. The Skill maps this friction, finds existing CI and GitHub features fall short, and recommends a read-only digest script as the first useful version. ## Quick Start Ask the assistant to map these recurring team frictions into an opportunity map and recommend whether to build, buy, complement, or wait.
