deliverable-step-report

Automating deliverable report generation involves rendering a Markdown template with project, node, and run context to create a standardized output. The report is then persisted to the .researchops/deliverables directory and attached as a run artifact for every step.

Uploading a Markdown report to a remote SSH path happens automatically when the project location is hosted remotely. The system detects the SSH target and transfers the generated deliverable report directly to the remote project directory.

Yes, deliverable reporting uses a template.md file to render the report content. It enforces quality by following guidelines defined in reference/x_guideline.md to ensure standardized output across all research runs.

Yes, the deliverable report skill works without external dependencies as it relies on internal rendering and metadata. It only requires an SSH connection if the project location is remote, otherwise it saves reports locally.

Generated research deliverable reports are stored locally in the .researchops/deliverables/<node_id>/<run_id>.md directory path. The system also records the deliverableReportPath in run metadata for easy retrieval.