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 ("build a dashboard") into observable, repeated pain points, then classifies each against existing tools, thin complements, and first useful versions. - Data Risk Assessment: Captures whether the first version runs on mock/local/read-only data or real company data, escalating access-control and auditability concerns early. - Decision Artifact: Produces a saved opportunity map (context/team/opportunity-map.md) with a comparison table, one recommended candidate, and a next-step routing to validation, shaping, or building workflows. - Use Case: A team lead notices engineers manually check which PRs block each release. The Skill classifies this signal, identifies a thin read-only complement over GitHub and CI data, and recommends a first useful version instead of a full platform build. ## Quick Start Ask the assistant to map 3-5 recurring team frictions into an opportunity map and recommend whether to build, buy, complement, or wait.
