name: omh-report-package
description: [omh] Hermes Report Package workflow: weekly/monthly reports, executive briefs, PPT-ready outlines, and upload packages. Use when the user says: report-package, report package, weekly report, monthly report, executive report, exec brief, leadership deck, status package.
metadata:
hermes:
tags: [workflow, oh-my-hermes, reporting]
category: reporting
phase: package-outline
role: operator
quality_tier: report-gated
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
- Current lane: Materials and visual summaries (
design-orchestration, design-quality-gate, frontend, accessibility-audit, visual-qa, content-operator, media-input-operator, materials-package, +4 more) - web, accessibility, visual QA, files, and packages.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when Hermes should turn supplied inputs into a report, executive brief, PPT-ready outline, or upload package without claiming presentation delivery.
Strong routing signals: `report-package`, `report package`, `weekly report`, `monthly report`, `executive report`, `exec brief`, `leadership deck`, `status package`, `ppt outline`, `presentation outline`, `slide outline`, `upload package`, `보고서 패키지`, `주간 보고서`, `월간 보고서`, `경영진 보고`, `리더십 보고`, `PPT`, `피피티`, `슬라이드`, `발표자료`, `업로드 패키지`
Catalog Metadata
Category: reporting
Phase: package-outline
Hermes role: operator
Quality tier: report-gated
Reasoning demand: standard
Quality bar:
- Name audience, reporting period, sections, supplied facts, assumptions, and missing data.
- Keep report packaging independent from reliability review unless explicitly requested.
- Export only Markdown/JSON outlines unless a separate presentation tool produces a binary deck.
Handoff policy:
Keep report narrative, sectioning, and Markdown/JSON outline packaging in Hermes; do not require reliability evidence unless the user asks for a reliability review.
Required inputs:
- audience
- reporting period or scope
- supplied facts
- missing data or assumptions
Expected outputs:
- report package
- PPT-ready Markdown or JSON outline
- assumptions and missing-input list
- optional achievements badge section sourced from
omh achievements export --format md when requested
Artifact expectations:
- operation_artifact/v1 report-package artifact when a wrapper or CLI records it
Safety rules:
- Do not claim source review completion from a prepared report package.
- Do not claim stakeholder approval or presentation delivery without observed evidence.
- Do not couple report packages to SLO, incident, or error-budget evidence by default.
Runtime Evidence
Preferred harness for this skill: report-package.
omh runtime record --skill report-package --harness report-package --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
