---
name: devhub-reports
description: Generate, save, review, approve, archive, retrieve, and copy XA DevHub reports grounded in current DevHub records. Use for report packets, daily, weekly, monthly, project, feedback, release drafts, health, validation, decision, handoff, or formal AI review reports and whenever Codex must control the report lifecycle.
---

# DevHub Reports

Reports are durable interpretations of a captured evidence packet. Use `$devhub-control` to obtain context and save the result.

## Role boundary

Use `$devhub-development` for active workflow direction, implementation, verification, resume state, AI review packets, and release readiness. Use `$devhub-knowledge` for source ingestion, durable claims, contradictions, and bounded Codex context. This skill owns report grounding, structure, status, approval, archival, release drafts, and formal saved review reports.

## Report workflow

1. Request `report-context` with the project, report kind, and period. This is an explicit capture mutation; use `report-preview` only for read-only inspection.
2. Record all five registry keys emitted by DevHub: report type, period start, period end, evidence timestamp, and `sha256:` input hash.
3. Draft from evidence. Label unsupported interpretation as inference.
4. Include overall status, summary, critical issues, warnings, recommendations, decisions, next actions, and source/evidence references when relevant.
5. Save as `draft` with all five registry keys, read it back, and compare it with its evidence packet.
6. Move to `approved` only when the user's request authorizes approval and factual checks, verification checks, and server-side registry validation pass. Use `archived` when superseded within the authorized scope; preparing a report alone does not approve it.

An active-work AI review bundle excludes completed notes by default, but it is context-only and cannot supply the registry keys for formal report approval. To formalize its findings, explicitly capture a separate `ai_review` report packet and save the report with that packet's five keys. Current report context includes both active work and bounded completed-period evidence, so keep those sections distinct and do not present completed history as part of the active review.

## Copied output routing

- Report packet: recommend `$devhub-reports` and the applicable domain skill.
- Resume packet: recommend `$devhub-development` and the applicable domain skill.
- Codex context: recommend `$devhub-knowledge` and the domain skill; add `$devhub-development` only when the live request authorizes edits.
- Release draft: recommend `$devhub-reports` and the release or domain skill; add `$devhub-development` only for separately authorized execution.
- AI review bundle: recommend `$devhub-development` and the domain skill; add `$devhub-reports` only for a formal saved review report.

Do not recommend `$devhub-control` in normal copied packets. Follow the copied-packet and release rules in [the development artifact contracts](../devhub-development/references/artifact-contracts.md).

Read [references/report-contracts.md](references/report-contracts.md) for lifecycle and grounding rules. Use [references/report-templates.md](references/report-templates.md) for the smallest applicable structure rather than forcing every section into every report.