05-learn

You can capture engineering solutions as reusable documentation by applying a schema-driven format to store resolved outcomes, pattern extractions, and completion context under a dedicated solutions directory for future retrieval.

To prevent duplicate knowledge management artifacts, the system evaluates overlap rules against existing documentation to decide whether to create a new frontmatter-rich artifact or update an existing one.

You need to write frontmatter schema documentation after a workflow loop completes or whenever you resolve a non-trivial problem that should benefit future planning and workflow review cycles.

Pattern extraction identifies recurring themes across existing artifacts and incorporates them into new documentation, ensuring newly stored solution artifacts capture established patterns alongside the specific resolution.

Yes, you can use grep to search structured engineering documentation because the system enforces schema consistency and uses a grep-first search strategy so later workflow skills can quickly find relevant learnings.

Yes, this approach supports evidence-first workflow closure by including context status and writing a handoff-lite record to ensure downstream workflow continuity after storing the solution artifact.