What problem does it solve? Legacy and long-lived repositories contain architecturally significant decisions that were never documented, leaving teams without the reasoning behind technology choices, infrastructure changes, and structural reshaping. ## Core Features & Use Cases - Git history mining: Sweeps commit messages, merge titles, dependency manifests, infrastructure files, and structural snapshots to detect architecturally significant changes. - Evidence-based triage: Clusters related commits into candidate decisions with confidence levels, detects reversals and superseded choices, and deduplicates against existing Decision Records. - Retroactive DR writing: Generates Decision Records following the log-decision conventions, with honest provenance notes, commit evidence links, and correct historical dates and authors. - Use Case: Point it at a five-year-old codebase with no ADR folder, and it will propose documented records for events like the migration from RabbitMQ to SQS or the adoption of a new framework, which you confirm before anything is written. ## Quick Start Run /backfill-decisions with an optional time range, path, or topic such as "2023..2024" or "database" to mine the repository history and generate Decision Records for confirmed past decisions.