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 Classification: Normalizes 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. - Candidate Recommendation: Ranks signals and recommends at most one candidate for a narrow, read-only, mockable first version, with a data-risk caveat. - Decision Artifact: Produces a saved opportunity map (context/team/opportunity-map.md) with a comparison table, recommended candidate, and next-step routing to validation, shaping, or building workflows. - Use Case: A team lead pastes notes about manual PR checks and ticket drift; the Skill classifies each signal, recommends a read-only digest script as the first useful version, and saves the map for later roadmap decisions. ## Quick Start Ask the assistant to map these recurring frictions into build, buy, complement, or wait decisions using the opportunity map skill.
