lidr-contract-extraction

This skill should be used when the user asks to "extract contracts", "generate contract registry", "bootstrap API contracts", "build the contract registry from repos", "scan repos for contracts", "crear contratos desde el código", "contract registry brownfield", "document contracts across repos". Self-configuring (capability probe + scenario routing) extraction of API / event / schema contracts from one or more repositories — monorepo OR multi-repo (e.g. backend/api, frontend, bridge, QA in separate repos the user has cloned locally) — into versioned contract specs (ADR-style) plus a derived contract-registry.yaml (document-project-style index) that lidr-impact-analysis then consumes. Works brownfield (derives contracts from existing code via framework introspection, annotations, traffic capture, or AI fallback). Do NOT use it to measure the impact of a change (use lidr-impact-analysis) nor to document prose architecture (use bmad-document-project). Output is English by default; artifact language follows the

By LIDR-IT schedule Updated 6/12/2026