Results Report
Write the complete post-experiment summary report after analysis artifacts are ready.
This skill is for the stage
after .
Role boundary
does
- strict statistics,
- real figures,
- figure interpretation scaffolding,
- stats appendix.
does
- complete experiment wrap-up report,
- decision-oriented narrative,
- figure-by-figure interpretation inside a coherent structure,
- limitations, failure cases, and next actions,
- Obsidian write-back into .
When the task is to create or redesign paper-ready figures/tables themselves, rely on
instead of expanding
into figure/table production.
Do not replace strict analysis with confident prose. If the analysis bundle is missing, first identify the blocker and request or produce the missing bundle.
Default output
The default report is an internal research report, not manuscript prose.
It should be named as:
text
YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.md
Example:
2026-03-18--freezing--r03--transfer-summary.md
2026-03-18--contrastive-adversarial--r02--ablation-report.md
The note title should be:
text
{Experiment Line} / Round {N} / {Purpose} / {YYYY-MM-DD}
Read
references/report-naming.md
before finalizing the filename or note title.
Required frontmatter
yaml
---
type: results-report
date: 2026-03-18
experiment_line: freezing
round: 3
purpose: transfer-summary
status: active
source_artifacts:
- analysis-output/analysis-report.md
- analysis-output/stats-appendix.md
linked_experiments:
- Experiments/Freezing-Study.md
linked_results:
- Results/Freezing-vs-Adapter.md
---
Default report structure
The report must include all sections below.
- Executive Summary
- Experiment Identity and Decision Context
- Setup and Evaluation Protocol
- Main Findings
- Statistical Validation
- Figure-by-Figure Interpretation
- Failure Cases / Negative Results / Limitations
- What Changed Our Belief
- Next Actions
- Artifact and Reproducibility Index
Read
references/report-structure.md
before writing.
Workflow
1. Confirm the report object
Lock these fields first:
- date,
- experiment line,
- round,
- purpose,
- linked experiment note,
- linked durable result note if one already exists.
If round is unknown, do not silently invent a semantic round. Use
only as a temporary placeholder and state that it should be normalized later.
2. Read the strict analysis bundle
Minimum required inputs:
- actual figures, if available
If these are missing, either generate them first with
or explicitly state which claims cannot be supported.
3. Write the report as a decision object
This report is not a transcript of outputs.
Each section must answer a real question:
- What did we test?
- What changed numerically?
- What is actually supported?
- What failed or remains uncertain?
- What should we do next?
Read
references/decision-oriented-analysis.md
for the expected reasoning depth.
4. Interpret figures inside the report
Do not only attach figures.
For each main figure:
- introduce why it is included,
- state the key observation,
- explain the supported interpretation,
- explain the decision implication.
Read
references/figure-interpretation.md
and
references/statistical-completeness.md
as needed.
5. Choose the write target explicitly
If the current repo is bound to an Obsidian project knowledge base:
- create or update
Results/Reports/{report-name}.md
- link back to the relevant note,
- update the matching canonical note when a durable conclusion is now supported,
- append a short trace to today's note,
- update
.claude/project-memory/<project_id>.md
If the repo is not bound:
- write the report as a local markdown artifact in the requested output location or next to the analysis bundle,
- keep the same filename contract,
- explicitly say that no Obsidian write-back was attempted.
Use
conventions only for bound repos. Internal experiment reports belong in
, not
.
6. End with explicit next actions
The report must end with operational decisions, for example:
- stop a weak branch,
- schedule one missing ablation,
- promote a stable finding into manuscript-facing writing,
- update the active plan.
Required quality bar
- The report must be dateable, searchable, and attributable to one experiment line and one round.
- The report must cite actual evidence from the analysis bundle.
- The report must include negative results when they matter.
- The report must separate stable conclusion from tentative interpretation.
- The report must say what changed in project belief and what should happen next.
Reference files
Load only what is needed:
references/report-structure.md
references/report-naming.md
references/figure-interpretation.md
references/statistical-completeness.md
references/decision-oriented-analysis.md
references/EVIDENCE-PROPAGATION.md
examples/example-results-report.md