AI & RAG

Weekly Digest of MRs Lacking Decision Coverage

Runs weekly to find merged MRs whose changes touch architecture not backed by any ADR, and publishes a Confluence page listing the documentation gaps for the team to fill.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList MRs merged in last 7 daysGitLabGitLab
  • ActionRetrieve existing ADR corpusConfluenceConfluence
  • ActionFlag undocumented architecture changesOpenAI
  • OutputPublish coverage-gap report to ConfluenceConfluenceConfluence

What it does

Once a week this flow reviews the MRs merged in the last seven days, retrieves the ADR corpus, and identifies changes that altered significant architecture without a corresponding decision record. It compiles these into a ranked "decision coverage gap" report and publishes it as a Confluence page, so the team can backfill the ADRs that should exist.

When to use it

Use it when your ADR practice is aspirational but enforcement is loose, and undocumented decisions keep accumulating. It makes the gap visible on a steady cadence instead of discovering it during an incident.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2The flow lists merged MRs from the past week via the GitLab API.
  3. 3Existing ADRs are retrieved from Confluence for matching.
  4. 4An OpenAI call flags MRs that changed architecture with no backing ADR and proposes a title for each missing record.
  5. 5A coverage-gap report is published as a Confluence page.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.