third-party-middleware

What problem does it solve?

Integrating, migrating, or stabilizing external middleware often crosses code and infrastructure boundaries and lacks repeatable, runtime-verified artifacts; this Skill exposes the middleware footprint, defines a single safe integration scope, and enforces verification so teams can close work only with runtime evidence.

Core Features & Use Cases

• Automated detection: repository scanner identifies middleware mentions and produces a machine-readable inventory for planning.
• Scoped integration planning: guidance for selecting exactly one integration scope (add, migrate, stabilize) with explicit boundaries and failure policies.
• CURDX artifact generation & verification: templates and recipes to populate research.md and tasks.md with POC/TDD steps, [VERIFY] checkpoints, VE startup/check/cleanup tasks, and runtime verification commands; useful for registries, caches, MQ, search, auth, and observability integrations.

Quick Start

Run the repository middleware detector and save a report by running the detect_middlewares.py scanner against the project root and writing output to a temporary JSON path.