[01] LOOP
DocsintervalHardened

Docs Until Accurate

Run the live app, compare docs against actual behavior, fix drift, and repeat until documentation matches reality.

by Trooper

Kickoff prompt
/loop 1d Start the "Docs Until Accurate" loop.

Goal: docs match live product behavior with drift fixes queued or published
Max iterations: 15
Between iterations run: Verify docs against live app behavior in browser
Exit when: no unaddressed doc drift remains or fixes are queued for approval

Step 1 — Monitor: Compare docs vs live app behavior.
Step 2 — Act: Fix drift, update screenshots, queue or publish.
Step 3 — Surface: Report remaining gaps and fixes applied.

## Before you start

Connect plugins:
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.
- Figma (required) — Inspect designs, dimensions, assets, and handoff notes.
- Notion (required) — Read and update approved briefs, docs, calendars, and reports.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Visual design QA (optional) — Compare implementation against visual expectations and capture regressions.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.
- Documentation QA (optional) — Check docs against current product behavior and keep claims accurate.
- Content operations (optional) — Turn signals into reviewable briefs while preserving source attribution.

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

Compare docs against live app — wrong steps, stale screenshots, missing features.

2. Act

Rewrite inaccurate sections, capture new screenshots, and queue or publish fixes.

3. Surface

Report drift found, fixes applied, and articles still needing review.

Flow diagram

Guardrails

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

  • Run the app — do not trust docs or code comments alone
  • Do not publish without the configured approval path
  • Capture fresh screenshots when UI steps changed

More Docs loops