knowledge-management-archetype-mapper

Maps domain requirements into a knowledge governance archetype model with sources, evidence, and freshness rules.

Updated Nov 19, 2020
One-click install
npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill knowledge-management-archetype-mapper-kwojtasinski-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-management-archetype-mapper
Source: https://github.com/kwojtasinski-repo/ECommerceApp/tree/main/.github/skills/knowledge-management-archetype-mapper
Command: npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill knowledge-management-archetype-mapper-kwojtasinski-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams building knowledge bases, RAG systems, or answer-with-citation features often conflate knowledge governance with document versioning, workflow, or audit logging, producing models that lack source traceability, freshness control, and confidence-aware trust. ## Core Features & Use Cases - Fit Test Gate: Runs an explicit archetype fit assessment before mapping and refuses domains that are really workflow, accounting, document-version, or audit problems. - Structured Mapping Workflow: Walks through knowledge value identification, clarifying questions, concept mapping, containers, operations, and traceability/freshness definitions. - Decision Sanity Check: Enumerates every embedded decision as requirement-sourced, asked, or silently assumed, and blocks delivery until business-impacting assumptions are resolved. - Use Case: Given "support agents answer questions from manuals and legal-approved policies, and every answer must cite its source", produce a complete model with knowledge objects, operations, freshness rules, and conflict reconciliation. ## Quick Start Ask the assistant to map your domain requirements into a Knowledge Management archetype model, describing what knowledge is managed, where it comes from, and who relies on it.

Frequently Asked Questions about knowledge-management-archetype-mapper

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

FAQPage Schema
How do I model a knowledge base with source traceability and citations?

Describe the domain requirements and run the mapping workflow: identify the knowledge value, map domain concepts to archetype concepts like Source, Evidence, and Assertion, then define freshness, confidence, and scope rules. The output is a complete implementable model with citation-backed derived answers.

When should I use a knowledge management archetype instead of a workflow model?

Use it when the natural question is "what do we know about X, from which source, how fresh is it, and can we cite evidence". If the question is about task state, quantities, or document versions, the fit test rejects the mapping and identifies the domain as workflow, accounting, or document-version instead.

Does this archetype handle conflicting sources in a knowledge base?

Yes, conflicting sources are modeled as a Relation between assertions plus an explicit reconciliation rule, such as one source type taking precedence. If the requirements do not specify a rule, the workflow asks a clarifying question rather than assuming one.

How are freshness and review cadence rules defined for knowledge items?

Each knowledge object gets a review cadence, valid-from and review-due fields, and an on-stale action such as hide, archive, warn, or re-approve. Variable cadences are passed in as externally computed parameters rather than hardcoded in the model.

What are the limitations of the knowledge management archetype?

It does not cover document version tracking, task or ticket state progression, audit trails proving what happened, or plain full-text search without governance concerns. Those belong to document, workflow, or audit models and are excluded by the fit test.