Report Package

Report Package

This is a Hermes-native report-package workflow skill.

Why This Exists

report-package exists to make reporting a first-class operations surface: Hermes can produce clean report and slide outlines while keeping approvals, delivery, and binary deck export as separate evidence.

Do Not Use When

• The user needs SLO, incident, or error-budget review; use reliability-review.
• The user asks for a live .pptx deck file rather than a PPT-ready outline.
• The request is meeting minutes, scrum history, or action-item tracking.

Examples

Good example:

• Prompt: report-package 월간 리더십 보고서 PPT outline 만들어줘.
• Expected behavior: Prepare a report package with sections, assumptions, missing inputs, and Markdown/JSON outline scope.
• Why: The request is packaging known information for reporting, not reliability validation or code work.

Bad example:

• Prompt: report-package prove our SLO passed and close the incident.
• Expected behavior: Route to reliability-review and require metric or incident evidence.
• Why: Report packaging cannot satisfy reliability closure evidence.

Completion Checklist

• The reporting window, inputs, audience, narrative, and evidence gaps are named.
• Draft report, generated package, approval, and delivery are separate states.
• The next action says whether to gather evidence, generate, revise, approve, or deliver.

Recovery Notes

• If input evidence is incomplete, mark the section as pending rather than fabricating a report claim.
• If delivery or attachment is unavailable, keep the report package prepared_not_observed.

Workflow Lane