What problem does it solve?
Teams often commit to custom-built mechanisms or adopt dependencies without structured due diligence, leading to unnecessary ownership costs, security exposure, or lock-in. This Skill enforces an evidence-backed decision process before committing to any material generic mechanism.
Core Features & Use Cases
- Three Proportionate Depths: Lightweight preflight for local capability checks, due diligence for prescribed dependencies, and full comparison for consequential unresolved choices.
- Evidence-Based Evaluation: Requires current primary sources (official docs, licenses, security advisories, changelogs) with recorded versions, dates, and URLs rather than popularity signals.
- Structured Decision Artifact: Produces an adopt, adapt, combine, build, defer, or do-nothing proposal using a decision template with hard gates, qualitative trade-offs, exit paths, and re-evaluation triggers.
- Use Case: Before building a custom feature-flag system, use this Skill to compare established open-source tools, managed services, and platform primitives against a genuine bespoke baseline, then record a proposed decision with ownership and exit strategy.
Quick Start
Use evaluate-existing-solutions to compare existing libraries and services against building our own solution for this scheduling mechanism before we commit.
