Menu
Run retrospectives, synthesize feedback and monitoring evidence, and plan the next iteration.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/LangeVC/skillweave --skill skillweave-post-releaseThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| 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]" |
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:
skillweave-observe for reports, metrics, and health dataThis skill does NOT implement a second health or monitoring subsystem. All observability data comes from skillweave-observe.
Jede Retrospektive folgt dieser Struktur:
## 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.
command="retrospective" kann einen observe-report einbetten:
skillweave-observe command="report" session="<id>" liefert Rohdaten
für die Retro-Diskussion (Timings, Fehler, Bottlenecks).skillweave-observe command="memory" session="<id>"
liefert decisions/gotchas aus dem Release-Session-Kontext.| 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 |
src/skillweave/post_release/retrospective.py — Retro-Vorlage, Report-Formatierungsrc/skillweave/post_release/feedback.py — GitHub Issue-Feedback, Kategorisierungsrc/skillweave/post_release/iteration.py — Backlog-Priorisierung, Plan-Formatierung| 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 |
