learning-capture

Capture development learnings by recording context-rich notes at specific trigger points, then route them to codebase documentation or plugin improvement workflows based on their content.

Document technical learnings after chat sessions for lightweight notes, after project completions for comprehensive retrospectives, and after overcoming blockers for targeted troubleshooting insights.

YAML frontmatter organizes retrospective documentation using a schema with fields like title, date, trigger, target, category, and tags, enabling structured search and routing to correct destinations.

Yes, this approach defines two output destinations: it integrates learnings into codebase documentation for architecture and troubleshooting, and routes them to plugin workflow spaces for future iterations.

Start logging project learnings by recording a concise learning note after your next chat session, then let the routing mechanism direct it to the appropriate codebase or plugin documentation target.

No, this learning capture method operates with no external dependencies, using a YAML frontmatter schema and defined trigger points to route notes to codebase docs or plugin improvement spaces.