AI & RAG
Postmortem Coverage Gap Detector
When a new postmortem is published, checks the existing corpus for whether a runbook already covers that failure mode and files a Linear task to write one if coverage is missing.
How it runs
The automated pipeline, trigger to output.
- TriggerPostmortem published in ConfluenceConfluence
- ActionRetrieve existing runbook coverage from PostgresPostgres
- ActionJudge coverage and draft runbook outlineOpenAI
- LogicBranch on covered vs gap
- OutputFile runbook task in Linear for gapsLinear
What it does
Every time a postmortem is published, this workflow asks a sharper question than 'what happened' — it asks 'do we have a runbook for this failure mode yet?' It retrieves against your existing runbook corpus, judges coverage, and when there's a gap it opens a Linear task to author the missing runbook.
When to use it
Use it to turn incidents into durable operational knowledge instead of one-off writeups. Ideal for teams that repeatedly relearn the same fixes because the postmortem never became a runbook.
How it works
- 1A new or updated postmortem in Confluence triggers the workflow.
- 2The postmortem's failure mode is embedded and matched against existing runbook chunks in Postgres.
- 3OpenAI judges whether current runbooks adequately cover this scenario and drafts a proposed runbook outline if not.
- 4A logic gate routes covered cases to a silent log and gap cases onward.
- 5For gaps, a Linear task is created with the outline, severity, and source postmortem link, assigned to the owning service team.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI & RAG workflows
Coda-grounded sales answer bot with citations in Slack
Reps ask product, pricing, or competitive questions in Slack and get an answer drawn only from your Coda knowledge hub, with links to the exact docs and rows it pulled from.
Weekly knowledge-gap digest from unanswered rep questions
Each week, scans rep questions the answer bot couldn't ground in Coda, clusters the recurring gaps.
Pre-meeting prep brief grounded in Coda and CRM
Before each booked sales meeting, builds a one-page prep brief by combining the account's HubSpot context with grounded talking points and objection responses pulled from your…
Publish a Grounded API FAQ Page to Confluence Weekly
Each week, clusters the top unanswered or repeated API questions, generates spec-grounded answers with citations.
Detect Breaking API Changes from Spec Diffs and Alert Owners
Compares the new OpenAPI spec against the previous version on each GitLab merge, uses retrieval over the changelog to classify whether changes are breaking.
Re-Index API Specs on GitLab Merge to Keep the Answer Bot Fresh
Watches GitLab merges to your API repo, detects changed OpenAPI specs and changelog files, re-chunks and re-embeds only what changed.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.