Close Retrospective — Post-Close Analysis

Last updated: April 17, 2026

Post-close analysis that reads how the close actually went — pace, review cycles, reassignments, reopens, workload balance. Produces a Slack-ready digest organized around questions a controller would actually ask, not raw statistics.

Before You Begin

  • Numeric MCP connected.

  • Numeric Toolkit installed.

  • At least one closed period (or an in-progress period — will be labeled "progress-to-date").

  • (Optional) Slack MCP for posting the digest to a channel.

How It Works

  1. Ask Claude for a retro. Example prompts:

    • "How did the close go?"

    • "Close retro for March 2026."

    • "Compare this close to last quarter."

    • "What took longest in Feb?"

  2. Claude asks which period and pulls tasks and events

  3. Claude computes defined metrics: turnaround, handoff rate, reopens, coverage gaps, workload concentration.

  4. Claude generates a plain-language digest andffers to post to Slack.

What You Get

A Slack-formatted digest with 7 sections:

  1. Quick numbers — KPI snapshot (completion %, turnaround, handoff rate, reopens, coverage gaps, churn)

  2. How's the pace? — first-touch latency, turnaround distribution

  3. Is the review process working? — handoff rate, reopens, rework cycle time, self-review

  4. Is work spread evenly? — concentration, most-loaded person, fastest/slowest, dormant tasks

  5. Setup gaps — unassigned tasks, missing due dates, high reassignment

  6. What went well / What to watch — auto-derived from the data

  7. Suggested actions — 1–3 concrete next steps

Optional dashboard: Ask Claude to generate a dashboard for you with scorecard tiles, pace chart, late-tasks table, review-friction table, assignee leaderboard.

Troubleshooting

Issue

What to Check

Digest took a long time

Scripts optimize calculations, but event batches are the bottleneck. For very large workspaces, consider capping the task count — the medians don't change much above ~150 tasks with events.

Digest feels generic

Customize and ask for specific questions you're interested in! Instruct Claude to add these to your question bank for future reference.

FAQ

  • Can I run it mid-close? Yes. Labels everything as "progress to date" and replaces cycle time with "Day X of Y."

  • Medians with <10 tasks? Works but noisy. Stick to raw counts for small periods.

  • Can I compare retros? Yes — say "compare this close to last quarter" and the skill pulls both periods.

Download & Install

Download the full Numeric Toolkit (15 community skills, including this one):

🔗 numeric-mcp-toolkit.zip

Install via Claude Code CLI:

/plugin marketplace add geoff-lew/numeric-toolkit
/plugin install numeric-mcp-toolkit

Direct link to the Skill

🔗 close-retro.zip

In Cowork, go to Customize in the left sidebar, click +, select the Skills tab, and click Install to upload the downloaded skill file.

Need help? Reach out to support@numeric.io.