Human Outcome Reporting
Explain what the user can now do, which requirements were verified, and what remains open. Works with Datarim or as a standalone skill.
A report you can understand on its own
Human Outcome Reporting 0.2.2 explains the product result before the internal activity. A progress update identifies a meaningful change; a final report connects the original request to the delivered outcome and the evidence. Missing checks, stale results, and checks on another version or environment remain visible.
What it changes
- Separate work performed, criteria verified, delivery, and human acceptance.
- Explain unfamiliar project terms where they appear.
- Use the appropriate profile for a feature, bugfix, research, operations, release, or ordinary answer.
- Keep the explanation complete; there is no hard word cap that hides an unmet requirement.
- Keep exact installation prompts, machine formats, permissions, and security controls intact.
Installation and use
Datarim commands load the shared skill from the project runtime. It can also be installed independently for Claude Code, Codex, and Cursor. See the reporting installation guide. Installing the skill does not install the Datarim workflow.
Explain again
/dr-explain restates an existing outcome or explains a term without changing files, running tests, deploying, or accepting the result.
How the pieces connect
The shared skill governs report meaning. Human Summary keeps the four familiar headings for QA, compliance, and archive. Commands, agents, templates, the requirement graph, and report records all refer to the same contract. Read the versioned source.
Limits
Automated validators check report structure and evidence bindings. They cannot guarantee that every reader understands an explanation, and discovering an installed skill does not prove that a particular client session loaded it.