{
  "schemaVersion": "1.0",
  "item": {
    "slug": "afrexai-knowledge-management",
    "name": "Knowledge Management System",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/1kalin/afrexai-knowledge-management",
    "canonicalUrl": "https://clawhub.ai/1kalin/afrexai-knowledge-management",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/afrexai-knowledge-management",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-knowledge-management",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "README.md",
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/afrexai-knowledge-management"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/afrexai-knowledge-management",
    "agentPageUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management/agent",
    "manifestUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Knowledge Management System",
        "body": "Turn tribal knowledge into searchable, maintained organizational intelligence. Stop losing expertise when people leave."
      },
      {
        "title": "Current State Assessment",
        "body": "Score each dimension 1-5 (1=nonexistent, 5=excellent):\n\nDimensionScoreEvidenceDocumentation coverage% of processes documentedFindabilityCan new hire find answers in <5 min?Freshness% of docs updated in last 6 monthsContribution culture% of team actively contributingOnboarding effectivenessTime to productivity for new hiresKnowledge retentionImpact when someone leavesCross-team sharingTeams accessing other teams' knowledge\n\nTotal Score: ___/35\n\nInterpretation:\n\n28-35: Mature — optimize and maintain\n21-27: Developing — fill gaps systematically\n14-20: Basic — needs foundational work\n7-13: Critical — knowledge is at risk"
      },
      {
        "title": "Knowledge Risk Register",
        "body": "knowledge_risk:\n  single_points_of_failure:\n    - person: \"[Name]\"\n      unique_knowledge: \"[What only they know]\"\n      risk_if_leaves: \"high|medium|low\"\n      extraction_priority: 1\n      extraction_method: \"interview|shadowing|recording|pair-work\"\n  \n  undocumented_processes:\n    - process: \"[Name]\"\n      frequency: \"daily|weekly|monthly|quarterly\"\n      complexity: \"high|medium|low\"\n      current_owner: \"[Name]\"\n      documentation_priority: 1\n  \n  tribal_knowledge:\n    - topic: \"[What people 'just know']\"\n      holders: [\"[Name1]\", \"[Name2]\"]\n      impact_area: \"[What breaks without it]\"\n      capture_method: \"interview|workshop|write-up\""
      },
      {
        "title": "Knowledge Extraction Interview Guide",
        "body": "For each single-point-of-failure person:\n\nContext: \"I'm documenting [X] so the team isn't dependent on any one person. This protects you too — less interruptions.\"\nProcess walk: \"Walk me through [X] from start to finish. I'll record/note.\"\nDecision points: \"Where do you make judgment calls? What factors do you consider?\"\nEdge cases: \"What are the weird situations that come up? How do you handle them?\"\nTools & access: \"What tools, credentials, or access do you need?\"\nHistory: \"Why is it done this way? What was tried before?\"\nGotchas: \"What are the things that trip people up?\"\n\nOutput format: Write up as a runbook (see Phase 3 templates)."
      },
      {
        "title": "Taxonomy Design",
        "body": "knowledge_taxonomy:\n  # Level 1: Knowledge Types\n  types:\n    how_to:\n      description: \"Step-by-step procedures and guides\"\n      examples: [\"Deploy to production\", \"Process a refund\", \"Set up dev environment\"]\n      template: \"runbook\"\n      \n    reference:\n      description: \"Facts, specs, configurations to look up\"\n      examples: [\"API endpoints\", \"Config values\", \"Vendor contacts\", \"Pricing tables\"]\n      template: \"reference_doc\"\n      \n    explanation:\n      description: \"Why things work the way they do\"\n      examples: [\"Architecture decisions\", \"Policy rationale\", \"Historical context\"]\n      template: \"explainer\"\n      \n    decision:\n      description: \"How to make specific judgment calls\"\n      examples: [\"Escalation criteria\", \"Approval thresholds\", \"Priority frameworks\"]\n      template: \"decision_tree\"\n      \n    troubleshooting:\n      description: \"Diagnosis and fix for known problems\"\n      examples: [\"Error codes\", \"Common failures\", \"Debug procedures\"]\n      template: \"troubleshooting_guide\"\n\n  # Level 2: Domains (customize per org)\n  domains:\n    - engineering\n    - product\n    - sales\n    - operations\n    - finance\n    - hr_people\n    - customer_success\n    - security\n    - legal_compliance\n\n  # Level 3: Topics (within each domain)\n  # Example for engineering:\n  engineering_topics:\n    - architecture\n    - deployment\n    - monitoring\n    - incident_response\n    - development_workflow\n    - testing\n    - security\n    - infrastructure"
      },
      {
        "title": "Information Architecture Rules",
        "body": "Maximum 3 levels deep — if deeper, reorganize\nOne canonical location per topic — link, don't duplicate\nEvery page has an owner — no orphan docs\nEvery page has a freshness date — reviewed within 6 months or flagged\nCross-references over duplication — \"See [X]\" beats copy-paste\nSearch-first design — assume people search, not browse"
      },
      {
        "title": "Naming Conventions",
        "body": "[DOMAIN]-[TYPE]-[TOPIC]-[SPECIFICS]\n\nExamples:\neng-howto-deploy-production\neng-ref-api-endpoints-v3\nsales-decision-pricing-enterprise\nops-troubleshoot-billing-failed-charges\nproduct-explain-auth-architecture"
      },
      {
        "title": "Navigation Structure",
        "body": "knowledge_base:\n  homepage:\n    - quick_links:  # Top 10 most-accessed pages\n    - recently_updated:  # Last 10 changes\n    - needs_review:  # Stale docs flagged\n    \n  by_audience:\n    new_hire: \"[Onboarding path → essential reading list]\"\n    engineer: \"[Dev setup → architecture → deployment → debugging]\"\n    manager: \"[Policies → processes → templates → reports]\"\n    customer_facing: \"[Product knowledge → troubleshooting → escalation]\"\n    \n  by_domain: \"[Taxonomy Level 2 domains]\"\n  by_type: \"[How-to | Reference | Explanations | Decisions | Troubleshooting]\""
      },
      {
        "title": "Runbook Template (How-To)",
        "body": "# [Title]: [Action verb] + [Object]\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]  \n**Estimated time:** [X minutes]  \n**Difficulty:** Easy | Medium | Advanced  \n\n## Prerequisites\n- [ ] [Access/tool/permission needed]\n- [ ] [Knowledge assumed]\n\n## Steps\n\n### 1. [First action]\n[Specific instruction with exact commands, clicks, or actions]\n\n> ⚠️ [Warning about common mistake at this step]\n\n### 2. [Second action]\n[Instructions]\n\n**Expected result:** [What you should see/get]\n\n### 3. [Continue...]\n\n## Verification\n- [ ] [How to confirm it worked]\n- [ ] [What to check]\n\n## Troubleshooting\n| Problem | Likely Cause | Fix |\n|---------|-------------|-----|\n| [Symptom] | [Why] | [Steps] |\n\n## Related\n- [Link to related runbook]\n- [Link to reference doc]"
      },
      {
        "title": "Reference Document Template",
        "body": "# [Subject] Reference\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]  \n**Scope:** [What this covers and doesn't cover]\n\n## Overview\n[1-2 sentence summary of what this reference contains]\n\n## [Main content organized as tables, lists, or structured data]\n\n| Item | Value | Notes |\n|------|-------|-------|\n| | | |\n\n## Quick Lookup\n[Most frequently needed items at the top]\n\n## Change Log\n| Date | Change | By |\n|------|--------|-----|\n| | | |"
      },
      {
        "title": "Architecture Decision Record (ADR)",
        "body": "# ADR-[NNN]: [Title]\n\n**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-[NNN]  \n**Date:** [YYYY-MM-DD]  \n**Deciders:** [Names]  \n\n## Context\n[What situation or problem prompted this decision?]\n\n## Decision\n[What was decided and why?]\n\n## Alternatives Considered\n| Option | Pros | Cons | Why rejected |\n|--------|------|------|-------------|\n| [A] | | | |\n| [B] | | | |\n\n## Consequences\n- **Positive:** [Benefits]\n- **Negative:** [Tradeoffs accepted]\n- **Risks:** [What could go wrong]\n\n## Review Date\n[When should this be revisited?]"
      },
      {
        "title": "Troubleshooting Guide Template",
        "body": "# Troubleshooting: [System/Process Name]\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]\n\n## Quick Diagnostic\n\n[Flowchart as text]\nIs [X] happening?\n→ YES: Go to Problem A\n→ NO: Is [Y] happening?\n→ YES: Go to Problem B\n→ NO: Go to Problem C\n\n## Problem A: [Symptom Description]\n\n**Likely causes (in order of probability):**\n1. [Most common cause]\n2. [Second most common]\n3. [Rare but possible]\n\n**Fix for Cause 1:**\n[Step-by-step resolution]\n\n**Fix for Cause 2:**\n[Step-by-step resolution]\n\n**Escalation:** If none of the above work → [who to contact, what info to provide]\n\n## Problem B: [Next symptom]\n[Same structure]"
      },
      {
        "title": "Decision Tree Template",
        "body": "# Decision Guide: [Topic]\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]\n\n## When to use this guide\n[Situation that triggers this decision]\n\n## Decision Flow\n\n### Step 1: [First question]\n- **If [condition A]** → [Action/next step]\n- **If [condition B]** → [Action/next step]\n- **If unsure** → [Default action or escalation]\n\n### Step 2: [Second question based on Step 1 answer]\n[Continue branching]\n\n## Override conditions\n[When to ignore this guide and escalate instead]\n\n## Examples\n| Scenario | Decision | Reasoning |\n|----------|----------|-----------|\n| [Real example] | [What was decided] | [Why] |"
      },
      {
        "title": "Writing Standards",
        "body": "The 4C Test (every document must pass all four):\n\nClear — Would a new hire understand this? No jargon without definitions.\nCorrect — Has this been verified by doing/testing? Not from memory.\nCurrent — Does this reflect how things work TODAY? Not 6 months ago.\nConcise — Can anything be cut without losing meaning? Cut it.\n\nFormatting rules:\n\nHeaders: action-oriented (\"Deploy to Production\" not \"Production Deployment\")\nSteps: numbered, one action per step, imperative mood\nWarnings: callout boxes, before the step (not after)\nCode/commands: exact, copy-pasteable, tested\nScreenshots: only if truly needed (they go stale fast)\nLinks: to canonical sources, never paste full URLs inline"
      },
      {
        "title": "Contribution Workflow",
        "body": "contribution_workflow:\n  create:\n    trigger: \"New knowledge identified (incident learnings, process change, new tool)\"\n    steps:\n      - choose_template: \"Match content type to template\"\n      - draft: \"Write using template structure\"\n      - self_review: \"Run 4C Test checklist\"\n      - peer_review: \"SME validates accuracy\"\n      - publish: \"Add to knowledge base in correct location\"\n      - announce: \"Notify relevant teams/channels\"\n    \n  update:\n    trigger: \"Existing doc is wrong, incomplete, or stale\"\n    steps:\n      - flag: \"Mark as needs-update with reason\"\n      - update: \"Make changes, update 'Last verified' date\"\n      - review: \"If significant change, get peer review\"\n      - publish: \"Update in place\"\n      - notify: \"If behavioral change, announce\"\n    \n  retire:\n    trigger: \"Doc no longer relevant (deprecated system, changed process)\"\n    steps:\n      - mark: \"Status: Deprecated, add redirect to replacement\"\n      - archive: \"Move to archive after 30 days\"\n      - redirect: \"Ensure all links point to replacement\""
      },
      {
        "title": "Incentivizing Contributions",
        "body": "Making it easy (remove friction):\n\nTemplates pre-filled with structure\n\"Quick capture\" channel — dump raw notes, someone structures later\nPost-incident: \"What would have helped?\" → becomes a doc\nPost-onboarding: new hire documents what was confusing\nMeeting notes → action items include \"document [X]\"\n\nMaking it visible (social proof):\n\nMonthly \"top contributors\" shoutout\n\"Docs champion\" rotating role — each sprint, one person owns doc health\nInclude documentation in performance criteria\nKnowledge sharing in team meetings (5-min \"TIL\" segment)\n\nMaking it expected (cultural norms):\n\n\"If you answered a question twice, write it down\"\nPR template includes \"Documentation updated? Y/N\"\nIncident postmortem includes \"Docs to create/update\"\nOnboarding feedback includes \"What couldn't you find?\""
      },
      {
        "title": "Search Optimization",
        "body": "Every document should be findable by:\n\nTitle — descriptive, includes key terms\nTags — domain, type, audience, technology\nSynonyms — include alternate terms people might search\nProblem description — \"When [X] happens\" phrasing\n\nTag schema:\n\ndocument_tags:\n  domain: \"[engineering|product|sales|ops|finance|hr|cs|security|legal]\"\n  type: \"[howto|reference|explanation|decision|troubleshooting]\"\n  audience: \"[all|engineering|management|customer-facing|new-hire]\"\n  technology: \"[list relevant tools/systems]\"\n  status: \"[current|needs-review|deprecated]\"\n  difficulty: \"[beginner|intermediate|advanced]\""
      },
      {
        "title": "Discovery Mechanisms",
        "body": "Contextual links — Related docs linked at bottom of every page\nFAQ collections — Per-domain \"frequently asked\" with links to full docs\nOnboarding paths — Curated reading lists by role\nSlack/chat bot — \"Ask the KB\" — searches and returns relevant docs\nWeekly digest — \"New & updated docs this week\" email/message\nError-page links — Application errors link to troubleshooting docs"
      },
      {
        "title": "Quality Signals",
        "body": "Prioritize search results by:\n\nFreshness — Recently updated > stale\nVerification — Peer-reviewed > unreviewed\nUsage — Frequently accessed > rarely accessed\nCompleteness — Fully structured > quick notes"
      },
      {
        "title": "Post-Incident Knowledge Capture",
        "body": "After every incident:\n\nImmediate (within 24h): Raw timeline and resolution steps\nPostmortem (within 5 days): Root cause, contributing factors, action items\nKnowledge extraction (within 10 days):\n\nNew troubleshooting guide? → Create from postmortem\nNew runbook needed? → Create from resolution steps\nExisting doc wrong? → Update with correct information\nArchitecture decision needed? → Write ADR\nMonitoring gap? → Document what to monitor"
      },
      {
        "title": "Post-Meeting Knowledge Capture",
        "body": "Meeting types that MUST produce knowledge artifacts:\n\nArchitecture review → ADR\nProcess change → Updated runbook\nStrategy decision → Decision record\nCustomer feedback pattern → Product knowledge update\nRetrospective → Process improvement doc"
      },
      {
        "title": "New Employee Knowledge Capture",
        "body": "First 30 days — new hire documents:\n\nWhat was confusing during onboarding\nQuestions that weren't answered by existing docs\nThings that were wrong in existing docs\nSuggestions for improvement\n\nTemplate for new hire feedback:\n\nonboarding_feedback:\n  week: \"[1|2|3|4]\"\n  couldnt_find: \n    - topic: \"[What they looked for]\"\n      where_looked: \"[Where they searched]\"\n      how_resolved: \"[Asked someone? Found eventually? Still unclear?]\"\n  wrong_or_outdated:\n    - doc: \"[Which document]\"\n      issue: \"[What's wrong]\"\n  suggestions:\n    - \"[Free text improvements]\""
      },
      {
        "title": "Exit Knowledge Transfer",
        "body": "When someone is leaving:\n\nIdentify unique knowledge — What do they know that no one else does?\nSchedule extraction sessions — 1-2 hours per major topic area\nRecord if possible — Video walkthroughs of complex processes\nPair them — Have successor shadow for final 2 weeks\nReview their authored docs — Are they complete? Assign new owners\nDocument tribal knowledge — \"Why\" questions only they can answer"
      },
      {
        "title": "Freshness Policy",
        "body": "freshness_policy:\n  review_frequency:\n    critical_operations: \"quarterly\"  # Deployment, incident response, security\n    standard_processes: \"semi-annually\"  # Regular workflows\n    reference_docs: \"annually\"  # Specs, contacts, architecture\n    explanations: \"annually\"  # Background, history, rationale\n    \n  review_process:\n    - owner_notified: \"2 weeks before due date\"\n    - review_actions:\n        - verify: \"Is this still accurate? Test/confirm.\"\n        - update: \"Fix any outdated information\"\n        - stamp: \"Update 'Last verified' date\"\n        - skip: \"If can't review, reassign or flag\"\n    - escalation: \"Unreviewed after 30 days → manager notified\"\n    - stale_threshold: \"2x review period without update → flagged as stale\""
      },
      {
        "title": "Content Health Dashboard",
        "body": "kb_health:\n  date: \"[YYYY-MM-DD]\"\n  \n  coverage:\n    total_documents: 0\n    by_type:\n      howto: 0\n      reference: 0\n      explanation: 0\n      decision: 0\n      troubleshooting: 0\n    by_domain: {}\n    gaps_identified: []\n    \n  freshness:\n    current: 0  # Reviewed within policy\n    needs_review: 0  # Due for review\n    stale: 0  # Past review deadline\n    deprecated: 0\n    freshness_rate: \"0%\"  # current / (current + needs_review + stale)\n    \n  quality:\n    peer_reviewed: \"0%\"\n    using_templates: \"0%\"\n    has_owner: \"0%\"\n    has_tags: \"0%\"\n    \n  usage:\n    searches_per_week: 0\n    failed_searches: 0  # Searches with no results\n    top_10_pages: []\n    pages_never_accessed: 0\n    \n  contribution:\n    docs_created_this_month: 0\n    docs_updated_this_month: 0\n    unique_contributors: 0\n    contribution_rate: \"0%\"  # contributors / total team size"
      },
      {
        "title": "Quarterly Knowledge Review",
        "body": "Agenda (60 min):\n\nDashboard review (10 min) — health metrics trend\nGap analysis (15 min) — what's missing? What questions keep being asked?\nStale doc triage (15 min) — update, deprecate, or reassign owners\nFailed searches review (10 min) — what are people searching for and not finding?\nProcess improvements (10 min) — what's working, what isn't?"
      },
      {
        "title": "Automated Knowledge Triggers",
        "body": "automation_triggers:\n  incident_resolved:\n    action: \"Create task: 'Write troubleshooting guide for [incident title]'\"\n    assignee: \"Incident commander\"\n    due: \"+10 days\"\n    \n  new_hire_started:\n    action: \"Generate personalized onboarding reading list from KB by role\"\n    \n  doc_stale:\n    action: \"Notify owner, CC manager if unreviewed after 14 days\"\n    \n  repeated_question:\n    threshold: \"Same question asked 3+ times in support/Slack\"\n    action: \"Create task: 'Document answer to [question]'\"\n    \n  process_changed:\n    trigger: \"PR merged that changes workflow/process\"\n    action: \"Check if related docs need updating, create task if yes\"\n    \n  failed_search:\n    threshold: \"Same search term fails 5+ times/week\"\n    action: \"Flag as gap, create task to write missing doc\""
      },
      {
        "title": "Knowledge-Powered Chatbot Design",
        "body": "kb_chatbot:\n  flow:\n    1_receive_question: \"User asks in designated channel\"\n    2_search: \"Semantic search across KB\"\n    3_respond:\n      found_match: \"Return relevant doc link + summary\"\n      partial_match: \"Return closest docs + 'Did you mean...?'\"\n      no_match: \"Log as gap, route to human expert, create doc task\"\n    4_feedback: \"Was this helpful? 👍/👎\"\n    5_improve: \"Use feedback to tune search, identify doc improvements\"\n    \n  sources:\n    - knowledge_base_docs\n    - slack_saved_answers  # Curated from Slack threads\n    - incident_postmortems\n    - meeting_notes_tagged_as_knowledge"
      },
      {
        "title": "Knowledge Sharing Mechanisms",
        "body": "MechanismFrequencyFormatAudience\"TIL\" channelDailyShort post (1-3 sentences + link)AllBrown bag lunchBi-weekly20-min presentation + Q&ACross-teamArchitecture reviewMonthly45-min deep dive + ADREngineeringCustomer insight shareMonthlyTop 5 patterns + implicationsProduct + CS + SalesPostmortem reviewPer incidentWritten + optional walkthroughEngineering + opsNew tool/technique demoAs needed15-min demo + doc linkRelevant teamsQuarterly knowledge reviewQuarterlyDashboard + gap analysisLeadership"
      },
      {
        "title": "Cross-Team Knowledge Map",
        "body": "knowledge_map:\n  engineering:\n    produces: [\"Architecture docs\", \"Runbooks\", \"API specs\", \"ADRs\"]\n    consumes_from:\n      product: [\"PRDs\", \"User research\", \"Roadmap\"]\n      customer_success: [\"Bug patterns\", \"Feature requests\", \"Usage data\"]\n      sales: [\"Technical requirements\", \"Integration needs\"]\n      \n  product:\n    produces: [\"PRDs\", \"User research\", \"Roadmap\", \"Release notes\"]\n    consumes_from:\n      engineering: [\"Technical feasibility\", \"Architecture constraints\"]\n      customer_success: [\"Feature requests\", \"Churn reasons\"]\n      sales: [\"Deal requirements\", \"Competitive intel\"]\n      \n  customer_success:\n    produces: [\"FAQ\", \"Troubleshooting guides\", \"Best practices\"]\n    consumes_from:\n      engineering: [\"Release notes\", \"Known issues\"]\n      product: [\"Feature docs\", \"Roadmap\"]\n      \n  sales:\n    produces: [\"Battlecards\", \"Competitive intel\", \"Use case docs\"]\n    consumes_from:\n      product: [\"Feature docs\", \"Roadmap\", \"Pricing\"]\n      customer_success: [\"Case studies\", \"Success metrics\"]\n      engineering: [\"Technical capabilities\", \"Integration docs\"]"
      },
      {
        "title": "Knowledge Management KPIs",
        "body": "MetricTargetMeasurementTime to answer<5 min for documented topicsSample timing testsNew hire time to productivityReduce by 30%First solo task dateRepeated questionsDecrease 50% in 6 monthsSupport ticket analysisDoc coverage>80% of critical processesAudit against process listFreshness rate>85% within review policyDashboard metricContribution rate>40% of team contributing monthlyContributor countSearch success rate>80% find what they needSearch analyticsFailed search rate<10% of searchesSearch analyticsKnowledge reuse>60% of team using KB weeklyUsage analytics"
      },
      {
        "title": "ROI Calculation",
        "body": "Knowledge Management ROI:\n\nTime Saved:\n  Reduced question-answering = [hours/week] × [avg hourly cost] × 52\n  Faster onboarding = [weeks saved] × [new hires/year] × [weekly cost]\n  Faster incident resolution = [hours saved/incident] × [incidents/year] × [hourly cost]\n  \nRisk Reduced:\n  Key person dependency = [probability of departure] × [knowledge reconstruction cost]\n  Compliance documentation = [audit prep hours saved] × [hourly cost]\n  \nQuality Improved:\n  Fewer repeated mistakes = [error rate reduction] × [cost per error]\n  Consistent processes = [variance reduction] × [rework cost]\n  \nTotal Annual Value = Time Saved + Risk Reduced + Quality Improved\nInvestment = Tool cost + Time spent maintaining KB + Training\nROI = (Total Annual Value - Investment) / Investment × 100"
      },
      {
        "title": "Document Quality Rubric (0-100)",
        "body": "DimensionWeight0-2 (Poor)3-5 (Adequate)6-8 (Good)9-10 (Excellent)Accuracy20%Unverified, possibly wrongMostly correctVerified, accurateTested, peer-reviewedCompleteness15%Major gapsCovers basicsComprehensiveEdge cases includedClarity15%Confusing, jargon-heavyUnderstandableClear, well-structuredA new hire gets itFindability10%No tags, bad titleSome tagsGood tags, clear titleSynonyms, cross-refsFreshness15%>12 months staleWithin annual reviewWithin semi-annualWithin quarterlyTemplate compliance10%No structurePartial templateFull templateTemplate + extrasActionability10%Theory onlySome stepsClear stepsCopy-paste readyOwnership5%No ownerOwner assignedOwner activeOwner + backup\n\nScore interpretation:\n\n90-100: Exemplary — reference model for other docs\n75-89: Good — meets standards\n60-74: Acceptable — needs minor improvements\n40-59: Below standard — needs significant work\n0-39: Critical — rewrite from scratch"
      },
      {
        "title": "Knowledge Base Health Score (0-100)",
        "body": "DimensionWeightMetricCoverage20%% of critical processes documentedFreshness20%% of docs within review policyQuality15%Average document quality scoreUsage15%% of team using KB weeklyContribution15%% of team contributing monthlySearch effectiveness15%% of searches finding results"
      },
      {
        "title": "Small Team (<10 people)",
        "body": "Start with a single shared doc/wiki, not a full KB platform\nFocus on: runbooks for critical processes, onboarding guide, decision log\nOne person owns KB health (part-time, not full-time)\nReview quarterly, not monthly"
      },
      {
        "title": "Remote/Distributed Teams",
        "body": "Default to written over verbal knowledge sharing\nRecord important meetings/decisions (not all meetings)\nAsync-first: every decision documented, not just discussed\nTime zone coverage: ensure docs cover \"what to do when the expert is asleep\""
      },
      {
        "title": "Rapid Growth (Doubling in 6 months)",
        "body": "Prioritize onboarding docs above all else\nImplement \"new hire documents what they learn\" from day 1\nAssign knowledge buddies — each new person paired with a doc mentor\nWeekly new-hire cohort Q&A → captured and documented"
      },
      {
        "title": "Regulated Industry",
        "body": "Map compliance requirements to documentation requirements\nVersion control with audit trail (who changed what, when)\nApproval workflows for regulated content\nRetention policies aligned with regulations"
      },
      {
        "title": "Post-Merger/Acquisition",
        "body": "Map both organizations' knowledge structures\nIdentify overlaps and gaps\nPrioritize: \"how do we work NOW\" docs over historical\nFreeze archives of legacy systems/processes"
      },
      {
        "title": "Migrating from Scattered Docs",
        "body": "Don't try to migrate everything — start fresh with new structure\nImport only: still-accurate, frequently-used docs\nRedirect old locations to new ones\nSet a sunset date for old system\n\"If it's not in the new KB, it doesn't exist\" (after migration period)"
      },
      {
        "title": "Natural Language Commands",
        "body": "CommandAction\"Audit our knowledge management\"Run Phase 1 assessment, generate risk register\"Design our KB structure\"Create taxonomy and navigation architecture\"Write a runbook for [X]\"Generate using runbook template\"Write an ADR for [X]\"Generate architecture decision record\"Create a troubleshooting guide for [X]\"Generate using troubleshooting template\"Review KB health\"Generate health dashboard and identify gaps\"Plan knowledge extraction for [person]\"Generate interview guide and schedule\"Set up freshness tracking\"Create review schedule and notification rules\"Design onboarding knowledge path for [role]\"Curate reading list from KB\"Analyze failed searches\"Review search gaps and create tasks\"Generate quarterly KB report\"Full metrics dashboard with recommendations\"Plan KB migration from [source]\"Create migration plan with prioritization"
      }
    ],
    "body": "Knowledge Management System\n\nTurn tribal knowledge into searchable, maintained organizational intelligence. Stop losing expertise when people leave.\n\nPhase 1: Knowledge Audit\nCurrent State Assessment\n\nScore each dimension 1-5 (1=nonexistent, 5=excellent):\n\nDimension\tScore\tEvidence\nDocumentation coverage\t\t% of processes documented\nFindability\t\tCan new hire find answers in <5 min?\nFreshness\t\t% of docs updated in last 6 months\nContribution culture\t\t% of team actively contributing\nOnboarding effectiveness\t\tTime to productivity for new hires\nKnowledge retention\t\tImpact when someone leaves\nCross-team sharing\t\tTeams accessing other teams' knowledge\n\nTotal Score: ___/35\n\nInterpretation:\n\n28-35: Mature — optimize and maintain\n21-27: Developing — fill gaps systematically\n14-20: Basic — needs foundational work\n7-13: Critical — knowledge is at risk\nKnowledge Risk Register\nknowledge_risk:\n  single_points_of_failure:\n    - person: \"[Name]\"\n      unique_knowledge: \"[What only they know]\"\n      risk_if_leaves: \"high|medium|low\"\n      extraction_priority: 1\n      extraction_method: \"interview|shadowing|recording|pair-work\"\n  \n  undocumented_processes:\n    - process: \"[Name]\"\n      frequency: \"daily|weekly|monthly|quarterly\"\n      complexity: \"high|medium|low\"\n      current_owner: \"[Name]\"\n      documentation_priority: 1\n  \n  tribal_knowledge:\n    - topic: \"[What people 'just know']\"\n      holders: [\"[Name1]\", \"[Name2]\"]\n      impact_area: \"[What breaks without it]\"\n      capture_method: \"interview|workshop|write-up\"\n\nKnowledge Extraction Interview Guide\n\nFor each single-point-of-failure person:\n\nContext: \"I'm documenting [X] so the team isn't dependent on any one person. This protects you too — less interruptions.\"\nProcess walk: \"Walk me through [X] from start to finish. I'll record/note.\"\nDecision points: \"Where do you make judgment calls? What factors do you consider?\"\nEdge cases: \"What are the weird situations that come up? How do you handle them?\"\nTools & access: \"What tools, credentials, or access do you need?\"\nHistory: \"Why is it done this way? What was tried before?\"\nGotchas: \"What are the things that trip people up?\"\n\nOutput format: Write up as a runbook (see Phase 3 templates).\n\nPhase 2: Knowledge Architecture\nTaxonomy Design\nknowledge_taxonomy:\n  # Level 1: Knowledge Types\n  types:\n    how_to:\n      description: \"Step-by-step procedures and guides\"\n      examples: [\"Deploy to production\", \"Process a refund\", \"Set up dev environment\"]\n      template: \"runbook\"\n      \n    reference:\n      description: \"Facts, specs, configurations to look up\"\n      examples: [\"API endpoints\", \"Config values\", \"Vendor contacts\", \"Pricing tables\"]\n      template: \"reference_doc\"\n      \n    explanation:\n      description: \"Why things work the way they do\"\n      examples: [\"Architecture decisions\", \"Policy rationale\", \"Historical context\"]\n      template: \"explainer\"\n      \n    decision:\n      description: \"How to make specific judgment calls\"\n      examples: [\"Escalation criteria\", \"Approval thresholds\", \"Priority frameworks\"]\n      template: \"decision_tree\"\n      \n    troubleshooting:\n      description: \"Diagnosis and fix for known problems\"\n      examples: [\"Error codes\", \"Common failures\", \"Debug procedures\"]\n      template: \"troubleshooting_guide\"\n\n  # Level 2: Domains (customize per org)\n  domains:\n    - engineering\n    - product\n    - sales\n    - operations\n    - finance\n    - hr_people\n    - customer_success\n    - security\n    - legal_compliance\n\n  # Level 3: Topics (within each domain)\n  # Example for engineering:\n  engineering_topics:\n    - architecture\n    - deployment\n    - monitoring\n    - incident_response\n    - development_workflow\n    - testing\n    - security\n    - infrastructure\n\nInformation Architecture Rules\nMaximum 3 levels deep — if deeper, reorganize\nOne canonical location per topic — link, don't duplicate\nEvery page has an owner — no orphan docs\nEvery page has a freshness date — reviewed within 6 months or flagged\nCross-references over duplication — \"See [X]\" beats copy-paste\nSearch-first design — assume people search, not browse\nNaming Conventions\n[DOMAIN]-[TYPE]-[TOPIC]-[SPECIFICS]\n\nExamples:\neng-howto-deploy-production\neng-ref-api-endpoints-v3\nsales-decision-pricing-enterprise\nops-troubleshoot-billing-failed-charges\nproduct-explain-auth-architecture\n\nNavigation Structure\nknowledge_base:\n  homepage:\n    - quick_links:  # Top 10 most-accessed pages\n    - recently_updated:  # Last 10 changes\n    - needs_review:  # Stale docs flagged\n    \n  by_audience:\n    new_hire: \"[Onboarding path → essential reading list]\"\n    engineer: \"[Dev setup → architecture → deployment → debugging]\"\n    manager: \"[Policies → processes → templates → reports]\"\n    customer_facing: \"[Product knowledge → troubleshooting → escalation]\"\n    \n  by_domain: \"[Taxonomy Level 2 domains]\"\n  by_type: \"[How-to | Reference | Explanations | Decisions | Troubleshooting]\"\n\nPhase 3: Document Templates\nRunbook Template (How-To)\n# [Title]: [Action verb] + [Object]\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]  \n**Estimated time:** [X minutes]  \n**Difficulty:** Easy | Medium | Advanced  \n\n## Prerequisites\n- [ ] [Access/tool/permission needed]\n- [ ] [Knowledge assumed]\n\n## Steps\n\n### 1. [First action]\n[Specific instruction with exact commands, clicks, or actions]\n\n> ⚠️ [Warning about common mistake at this step]\n\n### 2. [Second action]\n[Instructions]\n\n**Expected result:** [What you should see/get]\n\n### 3. [Continue...]\n\n## Verification\n- [ ] [How to confirm it worked]\n- [ ] [What to check]\n\n## Troubleshooting\n| Problem | Likely Cause | Fix |\n|---------|-------------|-----|\n| [Symptom] | [Why] | [Steps] |\n\n## Related\n- [Link to related runbook]\n- [Link to reference doc]\n\nReference Document Template\n# [Subject] Reference\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]  \n**Scope:** [What this covers and doesn't cover]\n\n## Overview\n[1-2 sentence summary of what this reference contains]\n\n## [Main content organized as tables, lists, or structured data]\n\n| Item | Value | Notes |\n|------|-------|-------|\n| | | |\n\n## Quick Lookup\n[Most frequently needed items at the top]\n\n## Change Log\n| Date | Change | By |\n|------|--------|-----|\n| | | |\n\nArchitecture Decision Record (ADR)\n# ADR-[NNN]: [Title]\n\n**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-[NNN]  \n**Date:** [YYYY-MM-DD]  \n**Deciders:** [Names]  \n\n## Context\n[What situation or problem prompted this decision?]\n\n## Decision\n[What was decided and why?]\n\n## Alternatives Considered\n| Option | Pros | Cons | Why rejected |\n|--------|------|------|-------------|\n| [A] | | | |\n| [B] | | | |\n\n## Consequences\n- **Positive:** [Benefits]\n- **Negative:** [Tradeoffs accepted]\n- **Risks:** [What could go wrong]\n\n## Review Date\n[When should this be revisited?]\n\nTroubleshooting Guide Template\n# Troubleshooting: [System/Process Name]\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]\n\n## Quick Diagnostic\n\n\n\n[Flowchart as text] Is [X] happening? → YES: Go to Problem A → NO: Is [Y] happening? → YES: Go to Problem B → NO: Go to Problem C\n\n\n## Problem A: [Symptom Description]\n\n**Likely causes (in order of probability):**\n1. [Most common cause]\n2. [Second most common]\n3. [Rare but possible]\n\n**Fix for Cause 1:**\n[Step-by-step resolution]\n\n**Fix for Cause 2:**\n[Step-by-step resolution]\n\n**Escalation:** If none of the above work → [who to contact, what info to provide]\n\n## Problem B: [Next symptom]\n[Same structure]\n\nDecision Tree Template\n# Decision Guide: [Topic]\n\n**Owner:** [Name]  \n**Last verified:** [YYYY-MM-DD]\n\n## When to use this guide\n[Situation that triggers this decision]\n\n## Decision Flow\n\n### Step 1: [First question]\n- **If [condition A]** → [Action/next step]\n- **If [condition B]** → [Action/next step]\n- **If unsure** → [Default action or escalation]\n\n### Step 2: [Second question based on Step 1 answer]\n[Continue branching]\n\n## Override conditions\n[When to ignore this guide and escalate instead]\n\n## Examples\n| Scenario | Decision | Reasoning |\n|----------|----------|-----------|\n| [Real example] | [What was decided] | [Why] |\n\nPhase 4: Contribution System\nWriting Standards\n\nThe 4C Test (every document must pass all four):\n\nClear — Would a new hire understand this? No jargon without definitions.\nCorrect — Has this been verified by doing/testing? Not from memory.\nCurrent — Does this reflect how things work TODAY? Not 6 months ago.\nConcise — Can anything be cut without losing meaning? Cut it.\n\nFormatting rules:\n\nHeaders: action-oriented (\"Deploy to Production\" not \"Production Deployment\")\nSteps: numbered, one action per step, imperative mood\nWarnings: callout boxes, before the step (not after)\nCode/commands: exact, copy-pasteable, tested\nScreenshots: only if truly needed (they go stale fast)\nLinks: to canonical sources, never paste full URLs inline\nContribution Workflow\ncontribution_workflow:\n  create:\n    trigger: \"New knowledge identified (incident learnings, process change, new tool)\"\n    steps:\n      - choose_template: \"Match content type to template\"\n      - draft: \"Write using template structure\"\n      - self_review: \"Run 4C Test checklist\"\n      - peer_review: \"SME validates accuracy\"\n      - publish: \"Add to knowledge base in correct location\"\n      - announce: \"Notify relevant teams/channels\"\n    \n  update:\n    trigger: \"Existing doc is wrong, incomplete, or stale\"\n    steps:\n      - flag: \"Mark as needs-update with reason\"\n      - update: \"Make changes, update 'Last verified' date\"\n      - review: \"If significant change, get peer review\"\n      - publish: \"Update in place\"\n      - notify: \"If behavioral change, announce\"\n    \n  retire:\n    trigger: \"Doc no longer relevant (deprecated system, changed process)\"\n    steps:\n      - mark: \"Status: Deprecated, add redirect to replacement\"\n      - archive: \"Move to archive after 30 days\"\n      - redirect: \"Ensure all links point to replacement\"\n\nIncentivizing Contributions\n\nMaking it easy (remove friction):\n\nTemplates pre-filled with structure\n\"Quick capture\" channel — dump raw notes, someone structures later\nPost-incident: \"What would have helped?\" → becomes a doc\nPost-onboarding: new hire documents what was confusing\nMeeting notes → action items include \"document [X]\"\n\nMaking it visible (social proof):\n\nMonthly \"top contributors\" shoutout\n\"Docs champion\" rotating role — each sprint, one person owns doc health\nInclude documentation in performance criteria\nKnowledge sharing in team meetings (5-min \"TIL\" segment)\n\nMaking it expected (cultural norms):\n\n\"If you answered a question twice, write it down\"\nPR template includes \"Documentation updated? Y/N\"\nIncident postmortem includes \"Docs to create/update\"\nOnboarding feedback includes \"What couldn't you find?\"\nPhase 5: Search & Discovery\nSearch Optimization\n\nEvery document should be findable by:\n\nTitle — descriptive, includes key terms\nTags — domain, type, audience, technology\nSynonyms — include alternate terms people might search\nProblem description — \"When [X] happens\" phrasing\n\nTag schema:\n\ndocument_tags:\n  domain: \"[engineering|product|sales|ops|finance|hr|cs|security|legal]\"\n  type: \"[howto|reference|explanation|decision|troubleshooting]\"\n  audience: \"[all|engineering|management|customer-facing|new-hire]\"\n  technology: \"[list relevant tools/systems]\"\n  status: \"[current|needs-review|deprecated]\"\n  difficulty: \"[beginner|intermediate|advanced]\"\n\nDiscovery Mechanisms\nContextual links — Related docs linked at bottom of every page\nFAQ collections — Per-domain \"frequently asked\" with links to full docs\nOnboarding paths — Curated reading lists by role\nSlack/chat bot — \"Ask the KB\" — searches and returns relevant docs\nWeekly digest — \"New & updated docs this week\" email/message\nError-page links — Application errors link to troubleshooting docs\nQuality Signals\n\nPrioritize search results by:\n\nFreshness — Recently updated > stale\nVerification — Peer-reviewed > unreviewed\nUsage — Frequently accessed > rarely accessed\nCompleteness — Fully structured > quick notes\nPhase 6: Knowledge Capture Workflows\nPost-Incident Knowledge Capture\n\nAfter every incident:\n\nImmediate (within 24h): Raw timeline and resolution steps\nPostmortem (within 5 days): Root cause, contributing factors, action items\nKnowledge extraction (within 10 days):\nNew troubleshooting guide? → Create from postmortem\nNew runbook needed? → Create from resolution steps\nExisting doc wrong? → Update with correct information\nArchitecture decision needed? → Write ADR\nMonitoring gap? → Document what to monitor\nPost-Meeting Knowledge Capture\n\nMeeting types that MUST produce knowledge artifacts:\n\nArchitecture review → ADR\nProcess change → Updated runbook\nStrategy decision → Decision record\nCustomer feedback pattern → Product knowledge update\nRetrospective → Process improvement doc\nNew Employee Knowledge Capture\n\nFirst 30 days — new hire documents:\n\nWhat was confusing during onboarding\nQuestions that weren't answered by existing docs\nThings that were wrong in existing docs\nSuggestions for improvement\n\nTemplate for new hire feedback:\n\nonboarding_feedback:\n  week: \"[1|2|3|4]\"\n  couldnt_find: \n    - topic: \"[What they looked for]\"\n      where_looked: \"[Where they searched]\"\n      how_resolved: \"[Asked someone? Found eventually? Still unclear?]\"\n  wrong_or_outdated:\n    - doc: \"[Which document]\"\n      issue: \"[What's wrong]\"\n  suggestions:\n    - \"[Free text improvements]\"\n\nExit Knowledge Transfer\n\nWhen someone is leaving:\n\nIdentify unique knowledge — What do they know that no one else does?\nSchedule extraction sessions — 1-2 hours per major topic area\nRecord if possible — Video walkthroughs of complex processes\nPair them — Have successor shadow for final 2 weeks\nReview their authored docs — Are they complete? Assign new owners\nDocument tribal knowledge — \"Why\" questions only they can answer\nPhase 7: Maintenance & Freshness\nFreshness Policy\nfreshness_policy:\n  review_frequency:\n    critical_operations: \"quarterly\"  # Deployment, incident response, security\n    standard_processes: \"semi-annually\"  # Regular workflows\n    reference_docs: \"annually\"  # Specs, contacts, architecture\n    explanations: \"annually\"  # Background, history, rationale\n    \n  review_process:\n    - owner_notified: \"2 weeks before due date\"\n    - review_actions:\n        - verify: \"Is this still accurate? Test/confirm.\"\n        - update: \"Fix any outdated information\"\n        - stamp: \"Update 'Last verified' date\"\n        - skip: \"If can't review, reassign or flag\"\n    - escalation: \"Unreviewed after 30 days → manager notified\"\n    - stale_threshold: \"2x review period without update → flagged as stale\"\n\nContent Health Dashboard\nkb_health:\n  date: \"[YYYY-MM-DD]\"\n  \n  coverage:\n    total_documents: 0\n    by_type:\n      howto: 0\n      reference: 0\n      explanation: 0\n      decision: 0\n      troubleshooting: 0\n    by_domain: {}\n    gaps_identified: []\n    \n  freshness:\n    current: 0  # Reviewed within policy\n    needs_review: 0  # Due for review\n    stale: 0  # Past review deadline\n    deprecated: 0\n    freshness_rate: \"0%\"  # current / (current + needs_review + stale)\n    \n  quality:\n    peer_reviewed: \"0%\"\n    using_templates: \"0%\"\n    has_owner: \"0%\"\n    has_tags: \"0%\"\n    \n  usage:\n    searches_per_week: 0\n    failed_searches: 0  # Searches with no results\n    top_10_pages: []\n    pages_never_accessed: 0\n    \n  contribution:\n    docs_created_this_month: 0\n    docs_updated_this_month: 0\n    unique_contributors: 0\n    contribution_rate: \"0%\"  # contributors / total team size\n\nQuarterly Knowledge Review\n\nAgenda (60 min):\n\nDashboard review (10 min) — health metrics trend\nGap analysis (15 min) — what's missing? What questions keep being asked?\nStale doc triage (15 min) — update, deprecate, or reassign owners\nFailed searches review (10 min) — what are people searching for and not finding?\nProcess improvements (10 min) — what's working, what isn't?\nPhase 8: Knowledge-Driven Automation\nAutomated Knowledge Triggers\nautomation_triggers:\n  incident_resolved:\n    action: \"Create task: 'Write troubleshooting guide for [incident title]'\"\n    assignee: \"Incident commander\"\n    due: \"+10 days\"\n    \n  new_hire_started:\n    action: \"Generate personalized onboarding reading list from KB by role\"\n    \n  doc_stale:\n    action: \"Notify owner, CC manager if unreviewed after 14 days\"\n    \n  repeated_question:\n    threshold: \"Same question asked 3+ times in support/Slack\"\n    action: \"Create task: 'Document answer to [question]'\"\n    \n  process_changed:\n    trigger: \"PR merged that changes workflow/process\"\n    action: \"Check if related docs need updating, create task if yes\"\n    \n  failed_search:\n    threshold: \"Same search term fails 5+ times/week\"\n    action: \"Flag as gap, create task to write missing doc\"\n\nKnowledge-Powered Chatbot Design\nkb_chatbot:\n  flow:\n    1_receive_question: \"User asks in designated channel\"\n    2_search: \"Semantic search across KB\"\n    3_respond:\n      found_match: \"Return relevant doc link + summary\"\n      partial_match: \"Return closest docs + 'Did you mean...?'\"\n      no_match: \"Log as gap, route to human expert, create doc task\"\n    4_feedback: \"Was this helpful? 👍/👎\"\n    5_improve: \"Use feedback to tune search, identify doc improvements\"\n    \n  sources:\n    - knowledge_base_docs\n    - slack_saved_answers  # Curated from Slack threads\n    - incident_postmortems\n    - meeting_notes_tagged_as_knowledge\n\nPhase 9: Cross-Team Knowledge Sharing\nKnowledge Sharing Mechanisms\nMechanism\tFrequency\tFormat\tAudience\n\"TIL\" channel\tDaily\tShort post (1-3 sentences + link)\tAll\nBrown bag lunch\tBi-weekly\t20-min presentation + Q&A\tCross-team\nArchitecture review\tMonthly\t45-min deep dive + ADR\tEngineering\nCustomer insight share\tMonthly\tTop 5 patterns + implications\tProduct + CS + Sales\nPostmortem review\tPer incident\tWritten + optional walkthrough\tEngineering + ops\nNew tool/technique demo\tAs needed\t15-min demo + doc link\tRelevant teams\nQuarterly knowledge review\tQuarterly\tDashboard + gap analysis\tLeadership\nCross-Team Knowledge Map\nknowledge_map:\n  engineering:\n    produces: [\"Architecture docs\", \"Runbooks\", \"API specs\", \"ADRs\"]\n    consumes_from:\n      product: [\"PRDs\", \"User research\", \"Roadmap\"]\n      customer_success: [\"Bug patterns\", \"Feature requests\", \"Usage data\"]\n      sales: [\"Technical requirements\", \"Integration needs\"]\n      \n  product:\n    produces: [\"PRDs\", \"User research\", \"Roadmap\", \"Release notes\"]\n    consumes_from:\n      engineering: [\"Technical feasibility\", \"Architecture constraints\"]\n      customer_success: [\"Feature requests\", \"Churn reasons\"]\n      sales: [\"Deal requirements\", \"Competitive intel\"]\n      \n  customer_success:\n    produces: [\"FAQ\", \"Troubleshooting guides\", \"Best practices\"]\n    consumes_from:\n      engineering: [\"Release notes\", \"Known issues\"]\n      product: [\"Feature docs\", \"Roadmap\"]\n      \n  sales:\n    produces: [\"Battlecards\", \"Competitive intel\", \"Use case docs\"]\n    consumes_from:\n      product: [\"Feature docs\", \"Roadmap\", \"Pricing\"]\n      customer_success: [\"Case studies\", \"Success metrics\"]\n      engineering: [\"Technical capabilities\", \"Integration docs\"]\n\nPhase 10: Metrics & ROI\nKnowledge Management KPIs\nMetric\tTarget\tMeasurement\nTime to answer\t<5 min for documented topics\tSample timing tests\nNew hire time to productivity\tReduce by 30%\tFirst solo task date\nRepeated questions\tDecrease 50% in 6 months\tSupport ticket analysis\nDoc coverage\t>80% of critical processes\tAudit against process list\nFreshness rate\t>85% within review policy\tDashboard metric\nContribution rate\t>40% of team contributing monthly\tContributor count\nSearch success rate\t>80% find what they need\tSearch analytics\nFailed search rate\t<10% of searches\tSearch analytics\nKnowledge reuse\t>60% of team using KB weekly\tUsage analytics\nROI Calculation\nKnowledge Management ROI:\n\nTime Saved:\n  Reduced question-answering = [hours/week] × [avg hourly cost] × 52\n  Faster onboarding = [weeks saved] × [new hires/year] × [weekly cost]\n  Faster incident resolution = [hours saved/incident] × [incidents/year] × [hourly cost]\n  \nRisk Reduced:\n  Key person dependency = [probability of departure] × [knowledge reconstruction cost]\n  Compliance documentation = [audit prep hours saved] × [hourly cost]\n  \nQuality Improved:\n  Fewer repeated mistakes = [error rate reduction] × [cost per error]\n  Consistent processes = [variance reduction] × [rework cost]\n  \nTotal Annual Value = Time Saved + Risk Reduced + Quality Improved\nInvestment = Tool cost + Time spent maintaining KB + Training\nROI = (Total Annual Value - Investment) / Investment × 100\n\nPhase 11: Scoring & Quality\nDocument Quality Rubric (0-100)\nDimension\tWeight\t0-2 (Poor)\t3-5 (Adequate)\t6-8 (Good)\t9-10 (Excellent)\nAccuracy\t20%\tUnverified, possibly wrong\tMostly correct\tVerified, accurate\tTested, peer-reviewed\nCompleteness\t15%\tMajor gaps\tCovers basics\tComprehensive\tEdge cases included\nClarity\t15%\tConfusing, jargon-heavy\tUnderstandable\tClear, well-structured\tA new hire gets it\nFindability\t10%\tNo tags, bad title\tSome tags\tGood tags, clear title\tSynonyms, cross-refs\nFreshness\t15%\t>12 months stale\tWithin annual review\tWithin semi-annual\tWithin quarterly\nTemplate compliance\t10%\tNo structure\tPartial template\tFull template\tTemplate + extras\nActionability\t10%\tTheory only\tSome steps\tClear steps\tCopy-paste ready\nOwnership\t5%\tNo owner\tOwner assigned\tOwner active\tOwner + backup\n\nScore interpretation:\n\n90-100: Exemplary — reference model for other docs\n75-89: Good — meets standards\n60-74: Acceptable — needs minor improvements\n40-59: Below standard — needs significant work\n0-39: Critical — rewrite from scratch\nKnowledge Base Health Score (0-100)\nDimension\tWeight\tMetric\nCoverage\t20%\t% of critical processes documented\nFreshness\t20%\t% of docs within review policy\nQuality\t15%\tAverage document quality score\nUsage\t15%\t% of team using KB weekly\nContribution\t15%\t% of team contributing monthly\nSearch effectiveness\t15%\t% of searches finding results\nEdge Cases\nSmall Team (<10 people)\nStart with a single shared doc/wiki, not a full KB platform\nFocus on: runbooks for critical processes, onboarding guide, decision log\nOne person owns KB health (part-time, not full-time)\nReview quarterly, not monthly\nRemote/Distributed Teams\nDefault to written over verbal knowledge sharing\nRecord important meetings/decisions (not all meetings)\nAsync-first: every decision documented, not just discussed\nTime zone coverage: ensure docs cover \"what to do when the expert is asleep\"\nRapid Growth (Doubling in 6 months)\nPrioritize onboarding docs above all else\nImplement \"new hire documents what they learn\" from day 1\nAssign knowledge buddies — each new person paired with a doc mentor\nWeekly new-hire cohort Q&A → captured and documented\nRegulated Industry\nMap compliance requirements to documentation requirements\nVersion control with audit trail (who changed what, when)\nApproval workflows for regulated content\nRetention policies aligned with regulations\nPost-Merger/Acquisition\nMap both organizations' knowledge structures\nIdentify overlaps and gaps\nPrioritize: \"how do we work NOW\" docs over historical\nFreeze archives of legacy systems/processes\nMigrating from Scattered Docs\nDon't try to migrate everything — start fresh with new structure\nImport only: still-accurate, frequently-used docs\nRedirect old locations to new ones\nSet a sunset date for old system\n\"If it's not in the new KB, it doesn't exist\" (after migration period)\nNatural Language Commands\nCommand\tAction\n\"Audit our knowledge management\"\tRun Phase 1 assessment, generate risk register\n\"Design our KB structure\"\tCreate taxonomy and navigation architecture\n\"Write a runbook for [X]\"\tGenerate using runbook template\n\"Write an ADR for [X]\"\tGenerate architecture decision record\n\"Create a troubleshooting guide for [X]\"\tGenerate using troubleshooting template\n\"Review KB health\"\tGenerate health dashboard and identify gaps\n\"Plan knowledge extraction for [person]\"\tGenerate interview guide and schedule\n\"Set up freshness tracking\"\tCreate review schedule and notification rules\n\"Design onboarding knowledge path for [role]\"\tCurate reading list from KB\n\"Analyze failed searches\"\tReview search gaps and create tasks\n\"Generate quarterly KB report\"\tFull metrics dashboard with recommendations\n\"Plan KB migration from [source]\"\tCreate migration plan with prioritization"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/1kalin/afrexai-knowledge-management",
    "publisherUrl": "https://clawhub.ai/1kalin/afrexai-knowledge-management",
    "owner": "1kalin",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management",
    "downloadUrl": "https://openagent3.xyz/downloads/afrexai-knowledge-management",
    "agentUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management/agent",
    "manifestUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/afrexai-knowledge-management/agent.md"
  }
}