summarize-to-knowledge

To convert project experiences into reusable knowledge, this Skill systematically captures decisions, lessons, and guidelines, writing actionable insights back into Kit content areas for future reference.

You should summarize project experiences for knowledge management at phase or task completion, allowing you to capture fresh decisions and lessons before moving to the next project stage.

Documenting knowledge in Kit requires read access to the Kit root directory and write access to content/knowledge and content/dev to update index documents and store captured insights.

The best way to update knowledge indexes after a project phase is to consolidate lessons and modify Kit index documents, such as content/knowledge/README.md, to reflect newly added topics.

Yes, you can create project retrospectives for dev content by applying this Skill at task completion to capture decisions and guidelines, writing them directly into the content/dev area.

Limitations include strict dependency on Kit-based environments and the necessity of following the workflow documented in METHODOLOGY.md, restricting use outside this specific content structure.