AI & RAG

Flag config values changed without an ADR and draft the missing rationale

On a schedule, this workflow finds config values that were changed in Git but have no linked ADR, drafts a rationale from the commit context.

CategoryAI & RAG
EngineSim + Paperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled gap scan fires
  • ActionBlame recent config changes and pull commits from GitLabGitLabGitLab
  • LogicKeep only changes with no linked or matching ADR
  • ActionDraft rationale from commit contextOpenAI
  • ActionCreate a draft ADR stub in ConfluenceConfluenceConfluence
  • OutputAlert the owning team in Slack to finalizeSlack

What it does

Hunts for accountability gaps: config values whose introducing commit cites no architecture decision record. For each gap, it drafts a candidate rationale from the commit message and diff context, creates a draft ADR stub in Confluence, and pings the owning team in Slack to confirm or correct it.

When to use it

When your ADR discipline has slipped and load-bearing settings exist with no recorded reasoning. Use it to backfill documentation debt steadily rather than in a painful one-time audit.

How it works

  1. 1A scheduled trigger runs the gap scan.
  2. 2The workflow blames recent config changes in GitLab and pulls each introducing commit.
  3. 3A logic step keeps only commits with no ADR reference and no matching ADR in Confluence.
  4. 4The agent drafts a rationale from the commit message, diff, and author.
  5. 5It creates a clearly-marked draft ADR stub in Confluence.
  6. 6It posts a Slack alert tagging the owner to review and finalize the stub.

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 SlackChannels, DMs, threads, mentions.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.