retrospective

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete new retrospective using template below.

UPDATE:

1. •Check document registry first, then search user's structure
2. •Preserve participant input and prior discussions
3. •Update actions, learnings, or follow-up items
4. •Show diff summary

FIND: Check registry, then search user's folders for retrospectives.

Conduct a Structured Retrospective for the specified project, launch, or time period.

V2V Phase

Phase 6: Learning & Adaptation Loop - This skill captures learnings for continuous improvement.

Output Structure

1. Retrospective Overview

• •Scope: What we're reviewing
• •Timeframe: Period covered
• •Participants: Who contributed
• •Facilitator: Who led

2. Context Summary

• •Original goals/objectives
• •Key deliverables planned
• •Resources allocated
• •Timeline planned vs actual

3. What Went Well 🟢

4. What Didn't Go Well 🔴

5. What We Learned 💡

6. Action Items

7. Process Improvements

8. Decisions to Revisit

9. Recognition

• •People who went above and beyond
• •Teams that collaborated exceptionally
• •Contributions worth highlighting

10. Follow-up Plan

Retrospective Facilitation Notes

For facilitators:

1. •Create psychological safety first
2. •Focus on systems, not blame
3. •Balance critique with recognition
4. •Drive to specific actions
5. •Assign owners and dates to everything

Instructions

1. •Ask about scope if not specified
2. •Check prior context: Run /relevant-learnings [topic] to see if we've learned similar lessons before
3. •Reference any project documents provided via @file syntax
4. •Distinguish root causes from symptoms
5. •Ensure every learning has an action
6. •Save as markdown file
7. •Offer to create presentation version using /present

Context Integration

After completing the retrospective:

1. •Offer to save learnings: Ask "Should I save these learnings to the context registry? (/context-save)"
2. •If yes, extract and save:
   • •Each learning to context/learnings/index.md with:
     • •Learning ID (L-NNN)
     • •Clear one-sentence insight
     • •Source (this retrospective)
     • •Category (Strategy/Product/GTM/Customer/Process)
     • •Confidence level
     • •Application guidance
3. •Update assumptions: If any assumptions were validated/invalidated, update context/assumptions/registry.md
4. •Flag re-decisions: If findings trigger re-decision criteria for past decisions, highlight this