_document-findings

Populates FINDINGS.md and updates HYPOTHESIS.md statuses from grep and read outputs.

2|1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/inference-sim/sdlc-plugins --skill document-findings-inference-sim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _document-findings
Source: https://github.com/inference-sim/sdlc-plugins/tree/main/plugins/hypothesis-test/skills/_document-findings
Command: npx skills add https://github.com/inference-sim/sdlc-plugins --skill document-findings-inference-sim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of documenting experiment results and updating hypothesis statuses, ensuring consistency and saving researchers significant time.

Core Features & Use Cases

  • Automated Reporting: Populates FINDINGS.md with experiment verdicts, metrics, and analysis.
  • Status Updates: Modifies HYPOTHESIS.md to reflect the outcome of each experiment.
  • Code-Level Analysis: Integrates with Grep and Read to trace findings back to specific lines of code for deeper understanding.
  • Use Case: After an experiment confirms a hypothesis, this Skill automatically updates the status to 'Confirmed', adds a detailed analysis of the results, and cites the exact code changes that led to the outcome.

Quick Start

Document the findings for the hypothesis in the 'hypotheses/h3-caching-latency' directory with a 'Confirmed' verdict, a summary, metrics table, and analysis output.

Frequently Asked Questions about _document-findings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document experiment findings and update hypothesis status automatically?

Document experiment findings by populating FINDINGS.md with verdicts, metrics, and analysis, while automatically modifying HYPOTHESIS.md status to reflect outcomes like 'Confirmed', saving manual reporting time.

Can I trace experiment results back to specific lines of code during documentation?

Yes, documenting experiment findings integrates Grep and Read tools to trace results back to specific code changes, enabling deeper code-level analysis and precise citation of the exact modifications that led to the outcome.

What is the best way to structure hypothesis-driven experiment reporting in markdown?

Structuring experiment reporting involves writing a summary, metrics table, and analysis output into FINDINGS.md, then updating the status in HYPOTHESIS.md within a defined hypothesis directory to maintain consistent experiment tracking.

Does documenting findings require existing markdown files to function correctly?

Yes, documenting findings requires reading existing HYPOTHESIS.md and related markdown files within a defined hypothesis directory to extract context, then writing new content and utilizing glob and grep tools for file system interaction.

How do I record a 'Confirmed' verdict for a caching latency hypothesis experiment?

To record a verdict, populate the FINDINGS.md file in the specific hypothesis directory with the 'Confirmed' status, add a detailed summary and metrics table, and automatically update HYPOTHESIS.md to reflect the confirmed outcome.