lesson-capture

You capture project lessons by recording specific mistakes, discoveries, and hard-won insights into structured files with standardized frontmatter. These operational knowledge files are then organized into dedicated directories to ensure consistent discovery and indexing for future reuse.

Documenting project lessons for agents and humans requires centralizing records by audience, saving them into separate structured directories. This ensures that both groups can quickly reference the specific operational knowledge relevant to their workflows during session initialization.

To structure markdown files for lesson discovery, you must apply standardized frontmatter to each file. This metadata enables consistent indexing and allows knowledge management systems to easily parse and surface the captured project lessons during future sessions.

Yes, you can use standard markdown to record project-specific mistakes and discoveries. The capture process relies on markdown formatting combined with standardized frontmatter to ensure the operational knowledge is structured correctly for automated discovery and human readability.

You need to save operational knowledge under specific lessons directories immediately after identifying a mistake, discovery, or hard-won insight. Placing these structured files in the correct directory ensures the knowledge is preserved and can guide future actions across agents and humans.

Organizing project lessons by audience improves workflow initialization by allowing agents and humans to read only the relevant structured files. This targeted knowledge reuse prevents repeating past issues and directly guides future actions within their specific operational context.