# Catch stale GitBook pages every Monday and queue them in Linear

> Every Monday morning, get a Linear ticket and a Slack heads-up listing the docs pages that have not been touched in 90 days.

- Workflow type: agent
- Services: GitBook, Linear, Slack Bot
- Categories: Product, Operations
- Published: 2026-06-26

## What it does

- Walks every space in your GitBook organization each Monday morning and finds pages whose last update is older than 90 days.
- Reads what each candidate page actually says and forms a short opinion on why it looks outdated, flagging old version numbers, deprecated UI references, and screenshots that probably no longer match.
- Opens one Linear issue per week with a tidy checklist of the top 10 stalest pages, each with a link, the last-updated date, and a one-line reason it stood out.
- Posts a short digest in your docs Slack channel with the link to the Linear issue so the team knows where to start.

## What you'll need

- A GitBook account with access to the organization you want audited.
- A Linear workspace and the teammate who should own the weekly docs cleanup ticket.
- A Slack workspace with our Slack Bot added to the channel where you want the digest posted.

## Prompt

Every Monday at 8am, sweep my GitBook organization for stale documentation and queue up the worst offenders for a refresh.

Walk all spaces with GitBook's List Organization Spaces, then List Pages In Space for each, and surface every page whose last revision is older than 90 days. Skip any space that looks like a changelog (title contains "changelog" or "release notes") and skip archived spaces and archived pages.

For each candidate page, pull the body with Get Page By ID, read what the page actually claims, and form a short opinion on whether it still reflects how the product works today. Look for version numbers that may be outdated, references to old UI elements (buttons, menu names, screen layouts), screenshots that the body implies but cannot be verified, and language that sounds like an older release. Combine the age signal and the content signal into a one-line reason this page looks stale.

Pick the 10 stalest pages (oldest plus highest staleness suspicion). Open one Linear issue using Create Issue titled "Weekly docs cleanup: top 10 stale GitBook pages" with a markdown checklist where each item is the page title, a link to the page, its last-updated date, and the one-line "why I think this is stale" note. Assign the issue to the docs owner and tag it with a docs-cleanup label if one exists.

Then Send a Message via Slack Bot to the #docs channel with a one-paragraph digest: how many spaces were scanned, how many stale pages were found in total, the names of the top 3 worst offenders, and a link to the Linear issue.

Hard rule: never open more than one Linear issue per week. If this Monday's run finds nothing meaningful (no pages older than 90 days), skip both the Linear issue and the Slack post and exit quietly.

## How to customize

- Change the day and time the sweep runs (default Monday at 8am).
- Adjust how old counts as stale (default 90 days) and how many pages land in the weekly checklist (default top 10).
- Pick which Slack channel gets the digest and who the Linear issue gets assigned to.
- Skip spaces you do not want audited, such as changelogs or archived projects, or narrow the sweep to a single space.

## FAQ

### Will this edit any of my GitBook pages?

No. The workflow only reads your pages to spot the stale ones. Every actual edit still happens by hand in GitBook, and the Linear ticket is the worklist.

### What counts as a stale page?

By default, any page that has not been updated in 90 days is a candidate. On top of the date check, the agent reads the page body and looks for clues like old version numbers, deprecated UI references, and language that no longer matches how your product works.

### Why one Linear issue per week instead of one per page?

Docs teams already get plenty of pings. A single weekly checklist keeps the noise down and gives the docs owner one place to triage, plan, and close out cleanup work.

### Can I limit it to a single GitBook space?

Yes. You can scope the sweep to one space, a list of spaces, or a collection during setup, and exclude spaces like changelogs or archives that should not be flagged.

### What if my team tracks work in Jira or GitHub Issues instead of Linear?

The workflow is easy to swap to another tracker like Jira, GitHub Issues, or Asana when you set it up. The rest of the flow stays the same.

Use this prompt in General Input: https://www.generalinput.com/prompts/catch-stale-gitbook-pages-every-monday-and-queue-them-in-linear