mcpField
A
analysis-retrospective

analysis-retrospective

github.com/nimrodfisherData & databases504211 installsUpdated 5w ago
Repository

About analysis-retrospective

A skill for reviewing completed analysis projects and recording what the team should repeat or change. It uses structured retrospectives, root-cause analysis, and tracked actions to turn project experience into reusable learning.

Key features

  1. 01Structured retrospective formats
  2. 02Plan-versus-actual review
  3. 03Root-cause analysis with 5-whys
  4. 04Reusable learning capture
  5. 05Action owners and due dates

Use cases

  1. 01Reviewing a completed analysis project
  2. 02Investigating late delivery or rejected work
  3. 03Running quarterly team retrospectives

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nimrodfisher/data-analytics-skills --skill analysis-retrospective

After installing, type/analysis-retrospectivein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
learnings_log_template.md
retrospective_template.md
references/
learning_capture.md
retro_frameworks.md

Details

From the project README

When to use

Within one week of completing a significant analysis project — while the details are still fresh. Also use after an analysis that went wrong (late delivery, stakeholder rejection, data error discovered post-delivery) to prevent recurrence. Run team retros quarterly even without a specific incident.

Process

  1. Time-box the retro — 30 minutes for solo, 60 minutes for team. Use the structured format in references/retro_frameworks.md to stay focused (Start/Stop/Continue or 4Ls: Liked/Lacked/Learned/Longed for).
  2. Review the project against plan — compare actual timeline, scope, and effort to what was planned; note the gaps.
  3. Identify what went well — capture at least two things that worked and should be repeated; these are as important as problems.
  4. Identify root causes of issues — for each problem, apply 5-whys to find the actual cause rather than the symptom.
  5. Capture reusable learning — use references/learning_capture.md to decide which learnings belong in: templates, reference docs, checklists, or team norms.
  6. Record and track actions — fill in assets/retrospective_template.md with owners and due dates; log durable learnings in assets/learnings_log_template.md.

Inputs the skill needs

  • Completed analysis project (name, scope, timeline)
  • Original plan or brief (for comparison)
  • Participants (solo or team members involved)

Output

  • Completed retrospective (retrospective_template.md) with what-went-well, issues, root causes, and action items
  • Learnings log entry (learnings_log_template.md) for reusable insights

Comments

Markdown supported