Project Retrospective (Grade A) logo

Project Retrospective (Grade A)Security-tested research skill for Claude AI. Grade A. Generate LESSONS.md retrospective files that capture institutional knowledge, especially failures. Use when closing out journalism projects, inve

— (0)
Daniel NikulshynReviewed by Daniel Nikulshyn·Updated July 2026

Overview

Project Retrospective (Grade A) is a security-tested research skill for Claude AI that generates LESSONS.md retrospective files. These files capture institutional knowledge, especially failures, and are useful when closing out journalism projects, investigations, events, or publications. The tool provides templates for research projects, event post-mortems, editorial tools, and publications. It encourages a blame-aware approach, acknowledging that pure blamelessness is unrealistic, and instead focuses on identifying system failures that permit human errors. The tool helps counter cognitive biases like fundamental attribution error, confirmation bias, hindsight bias, and negativity bias. It also promotes 'how' narratives over single-root-cause analysis, gathering information on cues, interpretation, goals, and actions. The tool is designed to be used when predefined triggers occur, such as live-event failures, editorial process failures, tool failures affecting subscribers, or stakeholder requests. The recommended cadence is to run retrospectives under one week after an incident, and aims to prevent 'retrospective theater' on routine work. The approach emphasizes specificity and honesty, similar to journalistic writing about one's own project. It frames retrospectives to deliberately counter the blame bias, rather than ignoring it. The tool seems well-suited for teams that want to learn from their failures and near-misses in a constructive, rather than punitive, way.

Key features

  • Generates LESSONS.md retrospective files
  • Provides templates for research projects, event post-mortems, editorial tools, and publications
  • Encourages 'how' narratives over single-root-cause analysis
  • Counters cognitive biases in incident analysis

Pricing

Model
Free
Category
Skills
Rating
No reviews yet

Use cases

Journalism Project Debrief

Use Project Retrospective to capture lessons learned from a investigative journalism project, including what went well and what didn't, to improve future projects.

Live Event Post-Mortem

Run a retrospective on a live event, such as an election night broadcast, to identify areas for improvement and document lessons learned.

Editorial Process Improvement

Use Project Retrospective to analyze and improve editorial processes, such as fact-checking and source management, to prevent future errors.

Pros & Cons

Pros

  • Encourages honest and specific reflection on project failures
  • Helps counter common cognitive biases in incident analysis
  • Promotes a blame-aware approach that acknowledges human error
  • Provides templates for various types of projects and incidents
  • Emphasizes learning from failures rather than assigning blame

Cons

  • May require significant cultural shift for teams not used to reflective practice
  • Can be time-consuming to complete retrospectives, especially for complex incidents
  • May not be suitable for teams with low psychological safety

Reviews

Sign in to leave a review.

No reviews yet. Be the first!

Q&A

What type of approach does it encourage?

It encourages a blame-aware approach, focusing on system failures that permit human errors, and 'how' narratives over single-root-cause analysis.

Asked by Margaret Whitfield · Feb 19, 2026

What biases does it counter?

It counters cognitive biases like fundamental attribution error, confirmation bias, hindsight bias, and negativity bias.

Asked by Wolfgang Krause · Jan 27, 2026

Is it suitable for all teams?

No, it may not be suitable for teams with low psychological safety and requires a cultural shift for teams not used to reflective practice.

Asked by Robert Ainsworth · Jan 5, 2026

What file type does it generate?

Project Retrospective generates LESSONS.md retrospective files.

Asked by Kirsi Laine · Dec 29, 2025

Ask a question

Skills alternatives

Using Git Worktrees (Grade A) logo
Using Git Worktrees (Grade A)Skills

Security-tested data-ai skill for Claude AI. Grade A. Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktre

— (0)
Free
Ga4 Bigquery Schema (Grade A) logo
Ga4 Bigquery Schema (Grade A)Skills

Security-tested data-ai skill for Claude AI. Grade A. GA4 BigQuery Export Schema Reference — complete field reference, nested structures, query patterns, and performance tips

— (0)
Free
Meta Capi (Grade A) logo
Meta Capi (Grade A)Skills

Security-tested data-ai skill for Claude AI. Grade A. Meta Conversions API (CAPI) Setup Reference — architecture, event types, customer information hashing, deduplication, implementation examples, AEM

— (0)
Free
Callees (Grade A) logo
Callees (Grade A)Skills

Security-tested development skill for Claude AI. Grade A. Lista o que uma funcao/metodo chama (call graph direto)

— (0)
Free
Test Module Name (Grade A) logo
Test Module Name (Grade A)Skills

Security-tested data-ai skill for Claude AI. Grade A. Name Haskell test modules after the module under test with a Spec suffix in the same namespace. Use when writing or reviewing Haskell test module

— (0)
Free
Board Of Directors (Grade A) logo
Board Of Directors (Grade A)Skills

Security-tested data-ai skill for Claude AI. Grade A. Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature designs, or any decisi

— (0)
Free
Advpl Mvc Avancado (Grade A) logo
Advpl Mvc Avancado (Grade A)Skills

Security-tested development skill for Claude AI. Grade A. MVC avançado via PE (Pontos de Entrada) — adicionar grids customizadas em telas MVC padrão (CNTA300/MATA070/MATA440/MATA460/FINA040 via *STRU)

— (0)
Free
D
Docs Writer (Grade A)Skills

Security-tested devops skill for Claude AI. Grade A. **WORKFLOW SKILL** — Maintains repository documentation accuracy and freshness across the docs site, agent files, and changelog. WHEN: "update docs

— (0)
Free