project-retrospective

Solid

Generate a LESSONS.md from a finished project: what worked, what didn't, what to reuse, what to retire — formatted for next-project carry-over.

AI & Automation 16 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Project Retrospective ## What This Skill Does Takes raw notes about a finished media project and generates a structured LESSONS.md that captures reusable editorial decisions, workflow fixes, timeline findings, and specific carry-over items for the next project. ## When To Use This Skill - After a series, season, or multi-episode project wraps and you want to capture what the team learned before everyone moves on to the next thing - When a project ran over budget, over schedule, or below quality expectations and you need a written record of why, without blame, before the post-mortem meeting - Before starting a new project that resembles one you finished recently — run the retrospective on the old project first, then use the LESSONS.md as a planning input - When a freelancer or contributor is leaving the team and their working knowledge needs to be captured before they go - At the end of a pilot or proof-of-concept phase, to decide whether the format is worth continuing and what must change if it does ## What You Need To Provide **Required:** - Project name and format (podcast series, documentary, article series, YouTube channel launch, newsletter run, etc.) - What the original brief or goal was — in one or two sentences - What was actually delivered — scope, episode count, word count, whatever the countable output was - What went well — even rough bullet points are fine - What went badly or took too long — same level of detail **Optional:** - Timeline: planned vs. actual...

Details

Author
ur-grue
Repository
ur-grue/autopunk-media-skills
Created
4 months ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

project-retrospective

Generate LESSONS.md retrospective files that capture institutional knowledge, especially failures. Use when closing out journalism projects, investigations, events, or publications. Includes templates for research projects, event post-mortems, editorial tools, and publications.

343 Updated today
jamditis
AI & Automation Solid

project-postmortem

Generate an evidence-grounded project retrospective — pulled from git history and decision docs, not memory — that grades the project on separate dimensions, splits what went right from wrong, reduces the failure to its root ordering error, extracts transferable lessons for the next project, and names what survives. Use whenever a project ships, stalls, or gets sunset and someone wants the writeup — "post-mortem", "retrospective", "what went wrong with X", "we're sunsetting X, write it up", or mid-project "why did this go sideways". The method cites commit hashes or sources for every claim, builds a timeline of when validation happened vs building, separates pros from cons including uncomfortable symmetries, and ends with a per-dimension scorecard plus a what-survives list — then runs a check that fails any vanity scorecard or uncited narrative. Distinct from drift-check (audits live docs) and conductor-memory/session-bookend (capture session state for continuity); this extracts backward-looking lessons.

0 Updated today
scoobydrew83
Testing & QA Listed

bmad-retrospective

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

8 Updated today
mouadja02