agent-learn

To capture project learnings after validation, update durable project context by refreshing PROJECT.md with feature details, creating ADRs in adr/, and appending retrospective notes to Tech Specs to preserve decisions for future work.

The best way to preserve architectural decisions is to create or update Architecture Decision Records in the adr/ directory, capturing the context, options considered, final decisions, and consequences to maintain durable project memory.

Update project memory after incident resolution by refreshing PROJECT.md with incident details and status, appending retrospective notes to Tech Specs, and creating ADRs to ensure the resolution context is preserved for future work.

Yes, you can document process friction alongside technical decisions. When capturing learnings and updating repository docs, you can include optional notes specifically detailing any process friction encountered during the workflow.

Capturing project context does not require manual onboarding updates. The process automatically refreshes repository onboarding docs and documentation to reflect newly learned patterns, ensuring onboarding stays current without separate manual intervention.

You should update tech specs with retrospective notes after a feature completes or an incident is resolved. Appending these notes ensures that learned patterns and process context are captured in project memory for future reference.