retrospect-domain Reference

Domain Frameworks

Technical Domain

  • What new patterns, APIs, or architectural approaches were discovered?
  • What technical decisions were made and why?
  • What implementation approaches worked well?
  • What approaches failed or would be done differently?
  • What edge cases or gotchas were encountered?
  • What technical debt was uncovered or paid down?

Research Domain

Load from the project-configurable domain frameworks location (e.g. domain-research.md) if available.

  • What hypotheses were tested?
  • What methods were used?
  • What insights emerged?
  • What sources were most valuable?

Generic Framework

  • What strategic insights emerged about the domain?
  • What customer/user needs were clarified?
  • What business decisions were made and their rationale?
  • What trade-offs were considered?
  • What assumptions were proven wrong?

Cross-Session Patterns

  • Recurring technical patterns or anti-patterns
  • Common decision-making themes
  • Areas of consistent success or struggle

Report Template

# Domain Retrospective: YYYY-MM-DD to YYYY-MM-DD

## Sessions Reviewed
- [List sessions with timestamps and brief summaries]

## Domain Learnings

### What I Learned
[Key discoveries, new patterns, insights about the domain]

### What Worked Well
[Successful approaches, good decisions, effective strategies]

### What Didn't Work
[Failed approaches, mistakes, what would be done differently]

### Decisions Made
[Key decisions and their rationale, trade-offs considered]

### Patterns Emerged
[Recurring patterns noticed across sessions]

## Start/Stop/Continue

### Start (Begin Doing)
[New practices to adopt]

### Stop (Avoid)
[Anti-patterns to eliminate]

### Continue (Maintain)
[Effective practices to keep]

## Action Items
- [ ] [Specific actions based on insights]

## Metrics Summary
- **Sessions**: N (technical/business/mixed breakdown)
- **Period**: [start date] to [end date]

---
Generated: [timestamp]

Key Principles

  • Extract, don’t invent: Base insights on actual session content
  • Be specific: Reference actual conversations, tools used, decisions
  • Detect patterns: Look for themes across multiple sessions
  • Domain-appropriate: Use domain frameworks for deeper insights
  • Framework flexibility: Adapt to session content type
Edit this page on GitHub