skill
Session retrospective, operator coaching, harness postmortem, codification, and outer-loop cycle critique. Turns evidence into hooks, rules, skills, backlog mutations, or explicit non-actions. Use when: "done", "wrap up", "what did we learn", "retro", "calibrate", "prompt better", "teach me from this session", "reflect on cycle", post-/flywheel critique. Trigger: /reflect, /retro, /calibrate, /reflect checkpoint <topic>, /reflect cycle <cycle-ulid>.
/reflect
Source: skills/reflect/SKILL.md
Session retrospective, operator coaching, harness postmortem, codification, and outer-loop cycle critique. Turns evidence into hooks, rules, skills, backlog mutations, or explicit non-actions. Use when: "done", "wrap up", "what did we learn", "retro", "calibrate", "prompt better", "teach me from this session", "reflect on cycle", post-/flywheel critique. Trigger: /reflect, /retro, /calibrate, /reflect checkpoint <topic>, /reflect cycle <cycle-ulid>.
Learn primitive in the Harness Kit operating loop.
This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.
Structured reflection that improves both the harness and the operator.
When roster receipts exist, include `.harness-kit/traces/` delegation receipts
in the evidence set when they are relevant. Reflection should convert
provider-lane results and failure modes into backlog, harness, or coaching
outputs without inventing hidden rankings.
## Delegation Floor
Delegation floor applies: probe the roster first; dispatch two or more
providers for substantive work; direct solo only for mechanical, emergency,
user-forbidden, or fewer-than-two-providers cases. See
`harnesses/shared/AGENTS.md` (Roster).
Local lane guidance: Use lanes to surface independent failure interpretations and improvement proposals; the lead owns synthesis and codification choices.
Every finding becomes one of three things:
- a codified artifact
- a concrete coaching note
- an explicit justification for not codifying
## Work Ledger
When `.harness-kit/work/ledger.jsonl` is available, `/reflect` consumes the
latest events for the active backlog/branch plus trace refs and delegation
receipts. It calls `scripts/work-ledger.py append` with `phase_started` at
retro start, `next_action_changed` when follow-up backlog or harness proposals
are emitted, and `phase_completed` when the reflection packet is complete.
Follow-up proposals are evidence refs, not hidden chat-only state.
## Routing
| Mode | Intent | Reference |
|------|--------|-----------|
| **distill** (default) | End-of-session retrospective -> codified artifacts + operator coaching | `references/distill.md` |
| **calibrate** | Mid-session harness postmortem — fix the harness before the code | `references/calibrate.md` |
| **coach** | Deep dive on prompt quality, technical specificity, and concept building | `references/coach.md` |
| **checkpoint** | Opt-in teach-back checkpoint with restatement, verdict, gaps, and gate artifact | `references/checkpoint.md` |
...