capturing-learnings

To capture project learnings automatically, you can use a structured documentation approach that records errors, user corrections, and feature requests into a dedicated `.learnings/` directory. This eliminates manual documentation efforts by aggregating information into standardized templates.

Continuous improvement pattern detection identifies repetitive learnings and errors across project work. It analyzes structured documentation records to find recurring issues, enabling teams to promote these insights into formal project documentation or new skills.

To set up a learnings directory, create a `.learnings/` folder in your project root and run the setup command. This copies the `LEARNINGS.md`, `ERRORS.md`, and `FEATURE_REQUESTS.md` templates from the skill assets into your directory to initialize tracking.

Yes, you can promote repetitive project errors into new skills or documentation. The pattern detection mechanism identifies frequent learnings from your structured records and elevates them to formal project documentation, ensuring recurring issues are systematically addressed.

Feature request management requires initial manual configuration of directories. You must create a `.learnings/` directory in your project root and copy the `FEATURE_REQUESTS.md` template from the skill assets before automated tracking begins.