knowledge-integration

Distill task learnings into structured knowledge integration proposals for master guidelines.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lshtram/core_dev --skill knowledge-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-integration
Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/knowledge-integration
Command: npx skills add https://github.com/lshtram/core_dev --skill knowledge-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distilling task-specific learnings into project-wide permanent records helps teams capture tacit knowledge, preserve learnings after task completion, and prevent knowledge loss across projects.

Core Features & Use Cases

  • Automated extraction: Pull key learnings from the task scratchpad (e.g., LEARNINGS_current.md) and categorize them into high-value items.
  • Guideline integration: Draft precise modifications to master guidelines files like CODING_STYLE.md, PROCESS.md, and COMPONENT_PATTERNS.md.
  • Proposal formatting: Produce a structured Knowledge Integration Proposal suitable for reviews and versioning.

Quick Start

Review LEARNINGS_current.md from the task scratchpad and produce a Knowledge Integration Proposal targeting the master guideline docs.

Frequently Asked Questions about knowledge-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn task learnings into permanent project documentation?

To turn task learnings into permanent project documentation, you distill high-value items from task scratchpads into a structured knowledge integration proposal for review. This proposal targets master guideline files to reduce knowledge loss and improve cross-task consistency.

What is the best way to update master guidelines with new process learnings?

Updating master guidelines with new process learnings involves extracting key insights from task scratchpads and drafting precise modifications to files like PROCESS.md and COMPONENT_PATTERNS.md. This ensures tacit knowledge is preserved across engineering, product, and design contexts.

How do I prevent knowledge loss across completed software development tasks?

Preventing knowledge loss across completed software development tasks requires capturing task-specific learnings into project-wide permanent records. You extract insights from scratchpads and format them into a structured proposal for master guideline updates.

Can I use a knowledge integration proposal to modify CODING_STYLE.md?

Yes, you can use a knowledge integration proposal to modify CODING_STYLE.md. The proposal drafts precise modifications for master guideline files and outputs modification notes suitable for YAML frontmatter and master guideline updates.

Does knowledge integration work for design and product contexts or only engineering?

Knowledge integration works across engineering, product, and design contexts. It distills learnings from the software development lifecycle into project-wide permanent records to improve cross-task consistency for all teams.