capture-learnings

To capture learnings and conventions as durable artifacts, you record the discovery so it persists in code, config, tests, AGENTS.md, or docs. It acts as an automatic gate at task end to route findings to the nearest governing document.

You should document conventions when gate criteria like high rediscovery cost, high blast radius, high frequency, low discoverability, or stale guidance apply. Persisting these non-obvious discoveries as artifacts ensures future work is faster and safer.

The best way to record code conventions in AGENTS.md is to trigger an automatic capture gate at task end. It evaluates your discoveries and routes the durable artifacts to the nearest governing document within the repository.

Knowledge management across code, config, and tests is handled by capturing non-obvious discoveries as durable artifacts. By applying a gate at task end, it automatically records conventions to the nearest project-local storage location.

Yes, you can persist project artifacts selectively by applying gate criteria such as gaps in existing documentation or stale guidance. It only records durable artifacts when these specific high-impact conditions are met.