edpa-reports

name	edpa-reports
user-invocable	false
description	Generate EDPA timesheets, reports, and exports. Produces per-person MD/JSON reports, per-item cost allocation, PI summaries, Excel exports, and frozen snapshots. Use when user asks for "reports", "výkazy", "export", "snapshot", or "per-item analysis". Requires edpa-engine results (edpa_results.json) as input.
license	MIT
compatibility	Python 3.10+ (openpyxl for XLSX), .edpa/config/people.yaml
allowed-tools	Read Write Bash(python3 *) Bash(cp *) Bash(mkdir *)
metadata	{"author":"Jaroslav Urbánek","version":"1.0.0","domain":"governance","phase":"reports","standard":"AgentSkills v1.0"}

EDPA Reports — Timesheet & Export Generation

What this does

Generates all EDPA output artifacts from engine results: per-person timesheets (MD+JSON), per-item cost allocation, frozen snapshots, PI summaries, and Excel exports.

Arguments

$ARGUMENTS = iteration ID, or "pi" for PI-level aggregation, or "per-item {item_id}" for single item analysis.

Argument resolution (when $ARGUMENTS is empty)

If $ARGUMENTS is empty, blank, or "help":

1. Read .edpa/config/edpa.yaml and extract pi.iterations
2. Check which iterations have existing results in .edpa/reports/iteration-{ID}/edpa_results.json
3. Present options:

   Available iterations:
     PI-2026-1.1  [closed]   1.4–14.4    results: yes
     PI-2026-1.2  [closed]   15.4–28.4   results: yes
     PI-2026-1.3  [closed]   29.4–12.5   results: yes
     PI-2026-1.4  [active]   13.5–26.5   results: no (run engine first)
     PI-2026-1.5  [planned]  27.5–9.6    (IP)
   
   Other options:
     "pi"                    PI-level aggregation across all closed iterations
     "per-item {item_id}"    Cost allocation for a single item (e.g., "per-item S-200")
   

4. Default suggestion: the latest closed iteration that has edpa_results.json.
5. Ask user: "Generate reports for which iteration? [suggested-id]"
6. If .edpa/config/edpa.yaml does not exist, inform user to run /edpa setup first.

Prerequisites

• .edpa/reports/iteration-{ID}/edpa_results.json exists (run edpa-engine first)
• .edpa/config/people.yaml exists

Output artifacts

Per-person reports (Iteration Close)

For each person, generate:

Markdown report (vykaz-{person}.md):

# VÝKAZ PRÁCE — {name}
Projekt: {project_name}
Registrace: {registration}
Období: {iteration} ({dates})
Kapacita: {capacity}h ({fte} FTE)
Metodika: EDPA 1.14.0-beta ({mode})

| Item | Typ | JS | CW | Score | Podíl | Hodiny |
|------|-----|----|----|-------|-------|--------|
| {rows} |
| **CELKEM** | | | | **{sum}** | **100%** | **{total}** |

Snapshot: {iteration}.json
Podpis (BankID): ☐ Čeká na podpis

JSON report (vykaz-{person}.json): Include all fields from edpa_results.json for this person plus project metadata and signature status.

Per-item cost allocation

For each item with ≥ 2 contributors:

ItemShare[P] = DerivedHours[P, item] / Σ DerivedHours[*, item]

Output hierarchically: Epic → Feature → Story with contributor breakdown per level. Engine writes both per-person summary and per-item allocation into a single workbook .edpa/reports/iteration-{ID}/edpa-results.xlsx with two tabs: Team Summary and Item Costs.

Frozen snapshot

Write to .edpa/snapshots/iteration-{ID}.json:

{
  "snapshot_version": "1.14.0-beta",
  "iteration": "{id}",
  "generated_at": "ISO-8601",
  "frozen": true,
  "methodology": "EDPA 1.14.0-beta",
  "capacity_registry": { "...from config..." },
  "edpa_results": { "...from engine..." },
  "signature_status": "pending"
}

FREEZE RULE: Once written, snapshot is immutable. Corrections create new revisions with incremented version suffix.

PI aggregation

When $ARGUMENTS = "pi":

1. Load all iteration results in current PI
2. Aggregate per person: Σ hours across iterations
3. Compare to expected (capacity × iterations_count)
4. Write .edpa/reports/pi-{ID}/pi-summary-{ID}.md

Excel export

Use openpyxl to create formatted XLSX:

import openpyxl
# Create workbook with sheets: Summary, Per-Person, Per-Item, Validation

Error handling

• Missing edpa_results.json → "Run edpa-engine for {iteration} first."
• Invariant failures in results → include warning banner in reports
• Snapshot already exists → create revision (iteration-{ID}_rev2.json)