learnings-curator

To manage technical notes and prevent stale knowledge, use a curation workflow that inspects, deduplicates, and rewrites scratchpad entries. This ensures task-specific findings are graduated to formal documentation or pruned entirely.

Organizing scratchpad findings into durable documentation requires strategic routing to determine if a note belongs in a task-specific file, project-wide docs, or global preferences. This routing ensures evidence-backed knowledge is captured durably.

You need to route debugging workarounds to project documentation when finishing a complex session to capture specific solutions. This prevents the next developer from repeating the same investigation and accumulating technical debt.

Knowledge management requires evidence-backed formatting for technical debt to maintain project documentation integrity. Consistent adherence to dated, verifiable evidence ensures that curated findings remain accurate and trustworthy over time.

Yes, you can deduplicate project scratch memory files automatically using intelligent curation scripts. These scripts inspect and rewrite entries in the project's learnings file to maintain high-quality, deduplicated documentation.