What problem does it solve? Teams often commit to new dependencies or build custom machinery without structured due diligence, leading to unnecessary ownership costs, lock-in, or reinvented wheels. This Skill enforces an evidence-backed decision process before adopting or building any material generic mechanism. ## Core Features & Use Cases - Three proportionate depths: lightweight preflight before proposing bespoke machinery, due diligence on a prescribed dependency, or a full market comparison for consequential choices. - Hard gates and qualitative trade-offs: eliminate candidates on hard constraints first, then compare finalists on total lifecycle ownership using the evaluation-dimensions reference. - Decision artifact: produces a structured adopt, adapt, combine, build, defer, or do-nothing proposal using the included decision template, with evidence ledger, exit path, and re-evaluation triggers. - Use Case: Before adding a validation library to a project, use this Skill to check the framework's built-in primitives, verify the candidate's maintenance and license status from primary sources, and record a proposed decision for the owner to accept. ## Quick Start Use evaluate-existing-solutions to decide whether we should adopt a library or build our own mechanism for this feature.
