analysis-retrospective

nimrodfisher's avatarfrom nimrodfisher

Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 11, 2026
[SOPs and Playbooks]

When & Why to Use This Skill

The Analysis Retrospective skill is designed to facilitate post-project learning and continuous process improvement. By systematically documenting lessons learned and refining analytical methodologies, it helps teams transform project experiences into actionable insights and standardized best practices for future success.

Use Cases

  • Project Post-Mortems: Conducting structured reviews after major analysis projects to identify successes, failures, and bottlenecks.
  • Process Optimization: Updating team SOPs and analytical playbooks based on documented lessons to improve efficiency and accuracy.
  • Knowledge Management: Building and maintaining a centralized learning repository to ensure organizational knowledge is preserved and accessible.
  • Continuous Improvement: Generating specific action plans and follow-up tasks to address identified weaknesses in team analytical practices.
nameanalysis-retrospective
descriptionPost-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

Analysis Retrospective

Quick Start

This skill helps you post-analysis learning and process improvement.

Context Requirements

Before proceeding, I need:

  1. Completed analysis: Key information needed for this analysis
  2. Retrospective template: Key information needed for this analysis
  3. Learning repository: Key information needed for this analysis
  4. Action follow-up: Key information needed for this analysis

Context Gathering

If any required context is missing from our conversation, I'll ask for it using these prompts:

For Completed analysis:

"To proceed with analysis retrospective, I need to understand completed analysis.

Please provide:

  • [Specific detail 1 about completed analysis]
  • [Specific detail 2 about completed analysis]
  • [Optional context that would help]"

For Retrospective template:

"To proceed with analysis retrospective, I need to understand retrospective template.

Please provide:

  • [Specific detail 1 about retrospective template]
  • [Specific detail 2 about retrospective template]
  • [Optional context that would help]"

For Learning repository:

"To proceed with analysis retrospective, I need to understand learning repository.

Please provide:

  • [Specific detail 1 about learning repository]
  • [Specific detail 2 about learning repository]
  • [Optional context that would help]"

Handling Partial Context

If you can only provide some of the context:

  • I'll proceed with what's available and note limitations
  • I'll use industry standard defaults where appropriate
  • I'll ask clarifying questions as needed during the analysis

Workflow

Step 1: Validate Context

Before starting, I'll confirm:

  • All required context is available or has reasonable defaults
  • The scope and objectives are clear
  • Expected outputs align with your needs

Step 2: Execute Core Analysis

Following best practices for analysis retrospective, I'll:

  1. Initial assessment - Review provided context and data
  2. Systematic execution - Follow structured methodology
  3. Quality checks - Validate intermediate results
  4. Progressive disclosure - Share findings at logical checkpoints

Step 3: Synthesize Findings

I'll present results in a clear, actionable format:

  • Key findings prioritized by importance
  • Supporting evidence and visualizations
  • Recommendations with implementation guidance
  • Limitations and assumptions documented

Step 4: Iterate Based on Feedback

After presenting initial findings:

  • Address questions and dive deeper where needed
  • Refine analysis based on your feedback
  • Provide additional context or alternative approaches

Context Validation

Before executing the full workflow, I verify:

  • Context is sufficient for meaningful analysis
  • No contradictions in provided information
  • Scope is well-defined and achievable
  • Expected outputs are clear

Output Template

Analysis Retrospective Analysis
Generated: [timestamp]

## Context Summary
- [Key context item 1]
- [Key context item 2]
- [Key context item 3]

## Methodology
[Brief description of approach taken]

## Key Findings
1. **Finding 1**: [Observation] - [Implication]
2. **Finding 2**: [Observation] - [Implication]
3. **Finding 3**: [Observation] - [Implication]

## Detailed Analysis
[In-depth analysis with supporting evidence]

## Recommendations
1. **Recommendation 1**: [Action] - [Expected outcome]
2. **Recommendation 2**: [Action] - [Expected outcome]

## Limitations & Assumptions
- [Limitation or assumption 1]
- [Limitation or assumption 2]

## Next Steps
1. [Suggested follow-up action 1]
2. [Suggested follow-up action 2]

Common Context Gaps & Solutions

Scenario: User requests analysis retrospective without providing context → Response: "I can help with analysis retrospective! To provide the most relevant analysis, I need [key context items]. Can you share [specific ask]?"

Scenario: Partial context provided → Response: "I have [available context]. I'll proceed with [what's possible] and will note where additional context would improve the analysis."

Scenario: Unclear objectives
→ Response: "To ensure my analysis meets your needs, can you clarify: What decisions will this inform? What format would be most useful?"

Scenario: Domain-specific terminology → Response: "I want to make sure I understand your terminology correctly. When you say [term], do you mean [interpretation]?"

Advanced Options

Once basic analysis is complete, I can offer:

  • Deeper investigation - Drill into specific findings
  • Alternative approaches - Different analytical lenses
  • Sensitivity analysis - Test key assumptions
  • Comparative analysis - Benchmark against alternatives
  • Visualization options - Different ways to present findings

Just ask if you'd like to explore any of these directions!

Integration with Other Skills

This skill works well in combination with:

  • [Related skill 1] - for [complementary analysis]
  • [Related skill 2] - for [next step in workflow]
  • [Related skill 3] - for [alternative perspective]

Let me know if you'd like to chain multiple analyses together.