forge-monitorlisted

# /forge:monitor — Monitoring & Observability ## When to Use - User says `/forge:monitor` - User wants to set up observability, define SLOs, check system health, or review metrics - Working in a Forge project at Stage 8 or 9 ## Pre-flight Check **Entry gate (REQ-GATE-ENTRY-001)** — before adopting the persona, verify the prior stage's artifact exists: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py preflight --stage 9 ``` If it exits non-zero, **STOP**: present its message verbatim and do not proceed — the prior stage must be completed first (or use `/forge:force-advance` to skip intentionally). 1. Read `pipeline/state.md` — confirm Forge project. 2. Confirm `pipeline/08-deploy/deploy-plan.md` exists (or `package-spec.md` for CLI/library projects). If neither: "Complete Stage 8 first (`/forge:deploy`)." 3. If stage > 9, ask if the user wants to update the health report. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 9` to load project-type overrides. **If the profile sets `skip: true` (library), skip this stage and report that monitoring is N/A for the project type.** Otherwise, treat each `additional_criteria` (e.g., API: 4xx/5xx alerts, p99 latency; ML: model drift, data quality, inference latency) as required SLI/SLO/alert entries. ## Steps 1. Read `agents/observer.md` to load the Observer persona. 2. Adopt that persona — you are now the Observer. 3. Read `pipeline/08-deploy/deploy-plan.md` and `pipeline/01-srs/srs.md`