knowledge-management

Classify, store, and retrieve project knowledge across sessions using structured memory frontmatter.

3|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill knowledge-management-bhaumikmaan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management
Source: https://github.com/bhaumikmaan/claude-code-master-skills/tree/main/skills/knowledge-management
Command: npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill knowledge-management-bhaumikmaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents loss of important project insights by classifying, storing, and retrieving knowledge that cannot be derived from the current codebase, ensuring continuity across sessions.

Core Features & Use Cases

  • Memory Taxonomy: Categorize information into user, feedback, project, and reference types with clear storage rules.
  • Safety Checks: Verify memory claims against the repository before acting, and enforce hygiene through duplication and staleness detection.
  • Layered Precedence: Merge global, user, project, and local memory sources with deterministic conflict resolution.
  • Use Cases: Remember a stakeholder’s preferences, capture a team decision about release dates, or store a reference to an external bug tracker for future queries.

Quick Start

Ask the assistant to remember that the user prefers Go over Python using the knowledge-management skill.

Frequently Asked Questions about knowledge-management

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

FAQPage Schema
How do I organize and recall project knowledge across sessions?

Project knowledge continuity across sessions is maintained by classifying information into user, feedback, project, and reference memory types using structured frontmatter and validation rules against the repository.

What is the best way to store stakeholder preferences and team decisions in a codebase?

The best way to store stakeholder preferences and team decisions is classifying them into user or project memory types with structured frontmatter, validating claims against the repository to prevent duplication and staleness.

How does memory taxonomy handle conflicting knowledge from global and local sources?

Conflicting knowledge from global, user, project, and local sources is resolved by a layered precedence system that merges memory sources with deterministic conflict resolution, ensuring consistent and accurate recall.

Can I verify memory claims against the repository before acting on them?

You can verify memory claims against the repository before acting on them; the system performs safety checks to validate stored knowledge and enforce hygiene through duplication and staleness detection.

When do I need structured memory frontmatter for project knowledge management?

Structured memory frontmatter is needed when capturing project insights that cannot be derived from the current codebase, ensuring continuity across sessions by applying taxonomy rules and validation against repository state.