Skill
Core
Human Summary
Compatible four-section recap for QA, compliance, and archive, governed by Human Outcome Reporting. Completeness before brevity.
One reporting contract
Human Summary loads Human Outcome Reporting first. It preserves the four headings expected by legacy callers and the Stop hook; it is a presentation adapter, not a competing source of truth.
The four sections
- What was done: restate the request and explain the achieved change.
- What worked: connect the delivered result to verified requirements and evidence.
- What did not work or is still open: disclose failures, missing checks, and limitations.
- What is next: a necessary action, with the existing command routing preserved.
Keep the task title and identifier for attribution. Emit one human recap; keep technical records in their authorized artifacts instead of pasting an internal technical block into chat. There is no hard word cap: completeness takes priority over brevity.
Callers
/dr-qa, /dr-compliance, and /dr-archive. For another explanation, use /dr-explain.