[01] LOOP
DocsintervalHardened

Self Managing Help Docs

Trooper watches your help center against what you shipped — stale articles, support repeats, broken guides — then rewrites content, updates screenshots, and surfaces coverage gaps.

by Trooper

Kickoff prompt
/loop 1d Start the "Self Managing Help Docs" loop.

Goal: help docs match the live product, updates are queued or published, and a coverage brief is delivered
Max iterations: 30
Between iterations run: Verify help articles against recent commits, support tickets, and live product behavior in browser
Exit when: doc drift is resolved or queued for approval and a surfaced coverage brief is delivered

Step 1 — Monitor: Watch help docs vs the live product — stale articles, repeat tickets, broken screenshots, shipped features with no docs.
Step 2 — Act: Rewrite articles, update step-by-steps, capture screenshots in browser, and queue or publish updates (respect approval gates).
Step 3 — Surface: Deliver a brief on outdated pages, top unanswered questions, and highest-impact articles to write next.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.

Steps

1. Monitor

Trooper watches your help center and your product — continuously. Stale articles, repeat support questions, broken screenshots, docs that don't match what shipped. Nothing slips through.

2. Act

Trooper doesn't just flag drift. Its agents rewrite articles, capture new screenshots, and publish updates — automatically, while you focus on shipping features.

3. Surface

Every gap becomes a clear next step. Know what's outdated, what users keep asking, and which articles would deflect the most support.

Flow diagram

Guardrails

Rules the agent must follow so it cannot cheat the exit condition.

  • Do not publish help center changes without the configured approval path
  • Describe user-facing behavior only — never document internal implementation details users cannot see
  • Run the app and capture screenshots when UI changed; do not leave placeholder images or TODO markers

More Docs loops