knowledge-framework

Automate MECE/BFO documentation structuring for Markdown files.

10|3|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/tekliner/improvado-agentic-frameworks-and-skills --skill knowledge-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-framework
Source: https://github.com/tekliner/improvado-agentic-frameworks-and-skills/tree/main/skills/knowledge-framework
Command: npx skills add https://github.com/tekliner/improvado-agentic-frameworks-and-skills --skill knowledge-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes examples (resource) components.

What problem does it solve?

This Skill eliminates the tedious manual work of inconsistent, unstructured, and untraceable documentation. It ensures all markdown content is clear, maintainable, and verifiable, saving time in understanding and updating complex information.

Core Features & Use Cases

  • MECE/BFO Structure: Organizes content into Mutually Exclusive, Collectively Exhaustive sections with proper ontological classification (Continuants vs. Occurrents).
  • Mermaid Diagrams: Automatically generates visual representations (TD for structure, LR for process) to enhance understanding.
  • Ground Truth Attribution: Mandates clickable sources (URLs, timestamps, code refs, session IDs) for every fact, ensuring verifiability and trust.
  • Use Case: When creating a new README.md for a complex system, this skill guides you to structure it with a thesis, overview, diagrams, numbered sections, and precise source attribution, making it instantly understandable and maintainable.

Quick Start

When creating any .md file, ask Claude: Document this using the Knowledge Framework. Claude will then guide you through the structured documentation process.

Frequently Asked Questions about knowledge-framework

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

FAQPage Schema
How do I structure markdown documentation to ensure clarity and consistency across teams?

Structure markdown using MECE (Mutually Exclusive, Collectively Exhaustive) principles to organize content into non-overlapping sections that collectively cover the topic. This eliminates redundancy, improves maintainability, and ensures every concept appears exactly once with clear attribution to its source.

What's the best way to add visual diagrams to technical documentation?

Use Mermaid diagrams within markdown to automatically generate visual representations. Apply top-down (TD) semantics for structural hierarchies and left-right (LR) for process flows, making complex systems instantly understandable without manual graphic creation.

How do I make documentation verifiable and traceable with source attribution?

Ground Truth attribution mandates clickable sources—URLs, timestamps, code references, or session IDs—for every fact in your markdown. This ensures verifiability, builds trust, and creates an auditable knowledge base that teams can confidently reference and update.

Can I organize markdown documentation using ontological principles?

Yes. Apply BFO (Basic Formal Ontology) classification to distinguish Continuants (entities that persist) from Occurrents (events and processes). This ontological alignment ensures semantic consistency and enables structured publishing to knowledge marketplaces.

What's the fastest way to create a well-structured README for a complex system?

Use the Knowledge Framework to guide README creation with a thesis, overview, mandatory diagram headers, numbered MECE sections, and Ground Truth source links. This produces instantly understandable, maintainable documentation without manual restructuring.

Does markdown documentation need a specific framework to avoid duplication and inconsistency?

Yes. The Knowledge Framework applies DRY (Don't Repeat Yourself) enforcement and fractal structure principles to markdown, preventing content duplication and ensuring consistency across all documentation files in your workflow.