knowledge-base-gap-finder · git:20260323.e34c23b · 2026-03-23 · sha256 c32f095f99f11b3b

knowledge-base-gap-finder git:20260323.e34c23bA

Immutable. This exact content never changes and is served at /api/v1/blob/c32f095f99f11b3b.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2nhrtxqh2djmiknz/c32f095f99f11b3b45c7d33edd9f5aed8f767299d7977bab116cb21f2dc0cccc.json

Then /plugin install knowledge-base-gap-finder@markdownregistry-2nhrtxqh2djmiknz in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: knowledge-base-gap-finder
description: Identify what documentation is missing by comparing support issues, product behavior, and existing docs. Use when the knowledge base is incomplete or stale.
---

# Knowledge Base Gap Finder

## Overview

Identify what documentation is missing by comparing support issues, product behavior, and existing docs.

## Core Workflow

1. Inspect the relevant diffs, configs, source files, or artifacts before forming a conclusion.
2. Compare the current state against repo conventions, expected guarantees, and known risk areas.
3. Prioritize the highest-impact gaps, regressions, or improvement opportunities instead of surface-level noise.
4. Recommend the smallest high-leverage changes and the checks that would validate them.

## Deliver

- Ranked findings or improvement opportunities with clear evidence.
- The main risks, tradeoffs, or regressions that matter most.
- Validation steps or follow-up edits that would reduce risk.

## Guardrails

- Lead with findings, not generic praise or low-value commentary.
- Use repo evidence and surrounding context instead of reviewing in isolation.
- Flag missing validation when a recommendation depends on behavior you could not confirm.
- Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.