Skillweave Post Release

---
facade: true
experimental: true
name: skillweave-post-release
description: "Run retrospectives, synthesize feedback and monitoring evidence, and plan the next iteration."
argument-hint: command="[retrospective|feedback|monitor|plan|health]" version="[version]"
---

# /skillweave-post-release

> Canonical metadata is English. User-facing artifacts follow the output language setting.

**Post-release lifecycle: retrospective interpretation, feedback synthesis, iteration planning.**

This skill handles what comes after a release goes live. It:
- **Consumes evidence from `skillweave-observe`** for reports, metrics, and health data
- **Owns retrospective interpretation** — synthesizing what went well, what to improve
- **Owns feedback synthesis** — categorizing and prioritizing community and system feedback
- **Owns iteration planning** — producing prioritized backlogs from retro + feedback

This skill does NOT implement a second health or monitoring subsystem. All observability data comes from `skillweave-observe`.

## Retro-Vorlage

Jede Retrospektive folgt dieser Struktur:

```markdown
## Retrospective v{version}

**Datum:** {date}
**Teilnehmer:** {participants}

### What went well
- {item}
### What to improve
- {item}
### Action Items
| Priority | Action | Owner |
|----------|--------|-------|
| P1       | {desc} | @user |
```

Action Items use P1 (blocker), P2 (next iteration), P3 (backlog) priority.

## Persistence

Retrospective reports are persisted automatically under the substrate contract:

- **Path:** `.skillweave/retrospectives/vX.Y.Z.md` (where X.Y.Z is the release version)
- **Durability:** DURABLE — retrospectives survive a fresh workspace
- **Disclosure:** SEALED — not disclosed outside the machine unless synced

Retrospectives authored at `.skillweave/retrospectives/vX.Y.Z.md` are carried to
the configured planning repository under `.skillweave/planning/retrospectives/`
via the planning-sync backing store. No manual copy is required.

## Observe Integration

- `command="retrospective"` kann einen observe-report einbetten:
  `skillweave-observe command="report" session="<id>"` liefert Rohdaten
  für die Retro-Diskussion (Timings, Fehler, Bottlenecks).
- Feedback wird mit Memory-Daten angereichert: `skillweave-observe command="memory" session="<id>"`
  liefert decisions/gotchas aus dem Release-Session-Kontext.

## Commands

| Command         | Description |
|-----------------|-------------|
| `retrospective` | Führt eine Retro durch. Nutzt Vorlage + observe-Integration. Output: Markdown-Report |
| `feedback`      | Sammelt Feedback aus GitHub Issues seit letztem Tag. Kategorisiert in bug/feature/improvement/question |
| `monitor`       | Ruft Metriken ab (via observe health endpoint + deployment metrics) |
| `plan`          | Erstellt Iterationsplan aus Retro + Feedback. Priorisiert nach urgency × effort |
| `health`        | System-Health-Check via observe health endpoint |

## Backend Modules

- `src/skillweave/post_release/retrospective.py` — Retro-Vorlage, Report-Formatierung
- `src/skillweave/post_release/feedback.py` — GitHub Issue-Feedback, Kategorisierung
- `src/skillweave/post_release/iteration.py` — Backlog-Priorisierung, Plan-Formatierung

## Testing

| Test Case | What to Validate |
|-----------|------------------|
| Retro-Vorlage korrekt | `create_retro_template("0.7.0")` liefert dict mit version, sections (4 keys), date |
| Feedback-Kategorisierung | `categorize_feedback()` trennt bugs/features/improvements/questions korrekt |
| Iteration-Backlog valide | `plan_iteration()` produziert sortierte Liste mit priority_score |
| Observe-Integration | Retro-Report enthält Hinweis auf observe-report-Einbettung |
| Action-Item-Priorisierung | P1-Items stehen vor P2/P3 in der sortierten Ausgabe |