Generate structured wave postmortem reports from milestone execution artifacts.
npx skills add https://github.com/ahlerjam/mmp --skill wave-postmortem
Please help me install this Agent Skill. Skill: wave-postmortem Source: https://github.com/ahlerjam/mmp/tree/main/skills/wave-postmortem Command: npx skills add https://github.com/ahlerjam/mmp --skill wave-postmortem
It turns messy, multi-phase milestone execution artifacts into a consistent, decision-ready wave postmortem with drift classification and actionable follow-ups.
gh is available) based on the recommendations contained in the generated report.Run /mmp:wave-postmortem to generate the wave postmortem report from the orchestrator wave state.
High-intent search queries and answers about installing and using this skill.
You can generate a wave retro report by running the wave-postmortem command on your milestone execution artifacts. It reads orchestrator status, audit event streams, and optional agent reflexion history to produce a structured markdown report.
MAST classification maps audit events to canonical failure-mode vocabulary clusters during retrospection workflows. It ensures consistent terminology across wave postmortem reports by standardizing how milestone execution drift and failures are categorized.
To create follow-up GitHub issues from postmortem recommendations, the gh command-line tool must be available and explicitly enabled. The skill gates issue creation, automatically generating GitHub issues based on recommendations contained in the generated report when configured.
Yes, you can run retrospection on archived milestone waves. The skill selects the correct state input by using specific wave IDs or live/archive flags, allowing you to generate deterministic postmortem reports from either live or archived wave data.
The best way to classify audit events for milestone management reports is using canonical MAST vocabulary. Mapping events to these predefined failure-mode clusters keeps terminology consistent and turns messy execution artifacts into decision-ready postmortem data.
No, you do not need the gh CLI installed to generate wave postmortem reports. The gh command-line tool is only required optionally for creating follow-up GitHub issues, and this feature must be explicitly enabled in your configuration.
intel-agencyAnalyze GitHub Actions workflow runs and artifacts into a structured post-mortem report.
baekenoughCollect and categorize release findings into actionable follow-up recommendations.
nrakowModel business processes as event streams for dbt-based implementations.
abrahamgreysonAutomate project checkpoint completion and phase progress documentation.