Use when triaging a log_warning, a PostHog $exception, or an auto-filed error-tracking GitHub issue (body contains "posthog-issue-") — decide expected no-op vs real defect and apply the escalation contract.
Use when picking up a GitHub issue through to a merged PR — branch naming, flow labels, phased-issue close rules, PR conventions, CI gates, and the release:now fast-lane policy.
Use when writing or modifying tests — choose the unit or integration lane, the right markers and mock fixtures, respect the hermetic autouse guards, and hit 80% patch coverage.
Use when filing an agent-ready GitHub issue for the autonomous pipeline — walks the .github/ISSUE_TEMPLATE/agent-task.yml form's Context/Scope/Acceptance/Verifier/Phase fields so MODE=start and phase_guard_ok can read something structured instead of guessing…
Use when a LinkedIn selector, scrape, or automation flow may have drifted, or before/after changing Selenium selectors — how to run the read-only live probe inside the selenium worker and read its JSON report.
Use when a deliverable (code, docs, or a UI change) needs to clear a REAL quality bar instead of just passing review — spin up isolated builder/critic pairs, blind-compare against a named reference exemplar, and loop until the build wins. Optional quality…
Use before starting implementation on any non-trivial LEM issue, feature, or task — nails down the Spec (testable acceptance criteria), the Verifier (the specific check that will decide success), and the Environment (which docs/skills/owning-module already…
Use when adding a feature flag, experiment, or PostHog-gated behavior toggle — FlagSpec registry, env fallback, call-site read, PostHog provisioning, and what must NOT be a flag.