Competitor Change Watch

/loop 1d Start the "Competitor Change Watch" loop.

Goal: competitor changes detected and sourced brief delivered
Max iterations: 30
Between iterations run: Verify competitor snapshots differ from last baseline with sources cited
Exit when: monitoring cycle complete with sourced change brief delivered

Step 1 — Monitor: Watch competitor sites, pricing, and changelogs.
Step 2 — Act: Diff against baseline, capture screenshots, classify impact.
Step 3 — Surface: Deliver sourced brief with suggested responses.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.
- Google Calendar (required) — Read upcoming meetings, attendees, and scheduling context.
- Slack (required) — Post summaries, approvals, blockers, and handoff updates.
- Notion (required) — Read and update approved briefs, docs, calendars, and reports.
- 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.
- Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped.
- Operations briefing (optional) — Summarize sources into concise, owner-aware, non-invented updates.
- Research monitoring (optional) — Compare sources over time and separate verified changes from noise.
- 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.