skill
Lightweight evidence-backed retro and catch-up reports for a current repo, branch, PR, backlog slice, or recent agent session. Use when the user asks for a debrief, catch me up, what changed, why it matters, product implications, end-user implications, developer experience implications, current app state, backlog state, workspace state, alternatives considered, or context rebuild after losing the thread. Trigger: /debrief.
/debrief
Source: skills/debrief/SKILL.md
Lightweight evidence-backed retro and catch-up reports for a current repo, branch, PR, backlog slice, or recent agent session. Use when the user asks for a debrief, catch me up, what changed, why it matters, product implications, end-user implications, developer experience implications, current app state, backlog state, workspace state, alternatives considered, or context rebuild after losing the thread. Trigger: /debrief.
Support primitive in the Harness Kit operating loop.
This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.
Produce a high-context explanation of what happened and why it matters.
Default to read-only. This is a catch-up and sensemaking skill, not a delivery
or codification skill.
Use `/reflect` instead when the main job is harness postmortem, operator
coaching, prompt debt, or writing follow-up codification. Use `/demo` when the
main job is a visual or runnable proof artifact. A debrief may point to either
as a next move.
## Evidence Stance
Start from live evidence. Prefer:
- `git status --short --branch --untracked-files=all`
- recent commits, staged diff, unstaged diff, branch/base comparison
- backlog files, PR descriptions, CI output, Dagger/test logs, trace receipts
- docs touched by the work, app routes or CLI help for changed surfaces
- screenshots or running app state only when the request needs rendered truth
Treat memory and chat history as leads, not truth. If evidence is missing,
stale, or too expensive to refresh, say that in `Sources & Gaps`.
Do not imply validation without the exact command, path, route, artifact, or
source that proves it. Separate confirmed facts, reasonable inference, and
opinion.
## Depth Control
Calibrate to the user's wording:
- "quick debrief", "where are we" -> concise report, no provider lanes unless
scope is broad or uncertain.
- "thorough", "comprehensive", "aggressive", "deep retro" -> probe roster and
use two or more provider lanes for independent interpretation or risk review.
- "right now" usually means prioritize useful synthesis over exhaustive
archaeology; name gaps instead of blocking on perfect history.
When using provider lanes, give them live artifacts only: diff, backlog, commit
range, traces, or docs. Do not leak the lead's conclusions.
## Delegation Floor
Delegation floor applies for substantive or broad debriefs: probe the roster
...