sparks-learn

You can capture project knowledge from conversations into reusable documentation by triggering a capture with a phrase like 'remember this detail about [topic]', reviewing the proposed learning, and saving it into the project's skill registry. This converts dialogue into structured, on-demand skills.

Documenting team decisions and patterns from chat logs is best handled by enforcing consistent structure and registry integration during knowledge capture. This ensures dialogue is transformed into well-formed, actionable skill entries that remain current for future reference.

Knowledge capture for onboarding works by converting past conversations and documented patterns into durable skills stored in the registry. New teammates can then load these learnings on demand to quickly understand project decisions and workflows.

Yes, you can load a previously saved learning from the skill registry into a new conversation. After the knowledge is captured and saved into the skill directory, you can retrieve and apply it on demand using the skill's name.

Knowledge capture does not require manual file management to keep documentation current. The process enforces required sections, verification steps, and registry integration to produce consistent, actionable learnings that stay up-to-date automatically.

You should not use automated knowledge capture from conversations when the dialogue lacks durable project value or when the information is transient. It is designed for preserving long-term decisions, patterns, and onboarding guidance, not for temporary operational chatter.