learning-capture

To capture learnings across sessions, provide a short title and description to generate a structured record. The system scans existing knowledge to link repeats before presenting a complete proposed record for your explicit approval.

Recurrence detection scans existing captured learnings to link repeating insights or surface related discoveries. It increments recurrence counts as needed, helping product teams identify recurring patterns across sessions and work orders.

You can document implementation insights with minimal input by providing just a title and description. The system handles structuring and context alignment, then presents a complete record for approval before any file creation occurs.

Yes, the governed workflow presents a complete proposed record for explicit approval before any file creation. This ensures structured learnings are reviewed before being committed to the central knowledge base.

Yes, CONTEXT.md updates are kept completely separate from the learning capture process. The workflow creates structured records independently, ensuring your context files remain modular and governed.

Building a cross-project knowledge base requires capturing learnings as structured records that align with current sessions and work orders. This enables cross-project reference and allows later promotions or context updates as insights compound.