DOCUMENT OPS
Weekly README staleness audit with Linear tickets
Every Monday, scans your ReadMe guides for pages that mention endpoints no longer in your shipped API surface and opens a Linear issue per stale page so docs debt gets triaged…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery Monday at 9am
- ActionList published guides from ReadMeReadMe
- ActionPull live route inventory from GitHubGitHub
- LogicFlag guides referencing dead endpoints
- LogicSkip pages with an existing open issueLinear
- OutputOpen a Linear issue per stale pageLinear
What it does
Runs a scheduled sweep of your ReadMe documentation, cross-references every code sample and endpoint reference against the live API surface pulled from GitHub, and turns each stale page into a tracked Linear issue with the specific mismatches listed.
When to use it
Use it when docs rot accumulates quietly and nobody owns cleanup. A weekly cadence keeps the audit lightweight while ensuring drift surfaces as actionable work rather than a once-a-year doc overhaul.
How it works
- 1A schedule trigger fires every Monday morning.
- 2The workflow pulls all published guides from ReadMe and the current route inventory from the GitHub repo.
- 3A logic step flags any guide referencing an endpoint, parameter, or method that no longer exists in the shipped surface.
- 4For each flagged guide it checks whether an open Linear issue already exists to avoid duplicates.
- 5It creates a Linear issue per newly stale page, labeled docs-drift, with the page URL and exact stale references in the description.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.