scorecardlisted

# Scorecard ## Core Rule Scorecard reports **numbers, not narrative**. It reads the audit log the `session-end.sh` hook writes — one JSON line per session — and arithmetic-aggregates it: how often the citation-gate ran versus failed, which guardrail hooks fired, how many times `SKIP_QUALITY_GATE=1` was used, how long sessions ran. It does **not** read your prose, judge your decisions, or recommend process changes. That is `/retro`. Scorecard is the instrument panel; the interpretation lives elsewhere. Per `CLAUDE.md → Model vs Code`, aggregating a JSONL telemetry log is deterministic — count, sum, divide. Do not estimate a pass rate from memory; compute it from the log. The model's only judgment here is **trend flagging**: noticing that citation-gate failures are climbing week over week is a signal worth surfacing, but the underlying counts must be exact. ## When to Use Invoke with `/scorecard` when: - You want a quick health read on the writing process — "are the gates passing, or am I fighting them?" - A `/retro` is about to run and wants the hard telemetry to anchor its qualitative review. - Citation-gate failures *feel* frequent and you want to confirm with numbers whether you are drafting ahead of your evidence. - You suspect `SKIP_QUALITY_GATE` is being reached for too readily — the log counts every bypass. - Periodically, to watch the guardrail-firing mix drift over a project's life. Scope the window with an argument: `/scorecard` defaults to the last ~10 sessio