after-task

What problem does it solve?

Mandatory knowledge capture after completing work. Documents solution in Graphiti and tracks effectiveness for system improvement.

Core Features & Use Cases

• Documents the solution in Graphiti (group_id="screengraph") with problem statement, solution approach, key learnings, modified files, and related specs/bugs
• Optional: Track MCP effectiveness to understand what patterns or MCPs actually helped and what could be improved for future specs

Quick Start

After finishing a spec or major task, document the solution in Graphiti and optionally record MCP effectiveness. Example: add_memory({ name: "[Spec/Bug Number]: [Short Title]", episode_body: ` [Tags: domain, type, technology]

**Problem**: [What we were trying to solve]

**Solution**: [High-level approach, not code details]

**Key Learnings**:
- [Learning 1]
- [Learning 2]

**Gotchas**:
- [Gotcha 1 with workaround]
- [Gotcha 2 with workaround]

**Files Modified**:
- [file 1]
- [file 2]

**Tests Added**:
- [test file 1]

**Related**: [Spec-XXX, BUG-YYY, FR-ZZZ]

**Date**: [YYYY-MM-DD]

`, group_id: "screengraph", source: "text" });

// Optional: track effectiveness track_effectiveness({ task: "[Original task description]", mcps_used: ["graphiti", "encore-mcp", "svelte"], outcome: "helpful", feedback: "[What worked well or what was missing]" });