Self Managing Help Docs

/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.

## Before you start

Connect plugins:
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.
- Google Analytics (required) — Read traffic, conversion, product, or campaign performance signals.
- Notion (required) — Read and update approved briefs, docs, calendars, and reports.
- Support tickets (required) — Read customer tickets, feedback, onboarding gaps, and support themes.
- CRM (required) — Read accounts, deals, owners, stages, and onboarding state.
- Linear / Jira (required) — Read roadmap, task, bug, owner, and status context.
- Figma (required) — Inspect designs, dimensions, assets, and handoff notes.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.
- Content operations (optional) — Turn signals into reviewable briefs while preserving source attribution.
- Customer operations (optional) — Identify at-risk accounts, missing setup steps, and safe next actions.
- Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial.
- Visual design QA (optional) — Compare implementation against visual expectations and capture regressions.
- Documentation QA (optional) — Check docs against current product behavior and keep claims accurate.

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.