knowledge-store
Query and build knowledge stores made with knowledge-store-builder. knowledge-store: ask a store questions (architecture, duplication, journeys, business intent), with every claim traced to evidence. knowledge-store-build: run the pipeline, including the summary, topic-brief and deep-dive authoring loops, and verify what subagents produce. knowledge-store-export: hand a finding to a ticket or a data-protection owner, with locations and masked shapes rather than the values themselves.
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin knowledge-store in hmcts/knowledge-store-builder. Commands read from the repo's manifest — 8 days ago.
What it installs
Skills (5)
technical-writerUse when writing or reworking any user-facing documentation in this repository — the README, the docs/ guides, skill prose. Enforces the house register - persona-led, value-first, no AI slop - and the verification that documentation is code.
knowledge-store-assessUse when a product or delivery team asks whether historic backlog tickets are still needed — has the platform since delivered, replaced or invalidated the requirement. Assesses each ticket against a committed knowledge store and returns, per ticket, a committed answer on whether the requirement is s
knowledge-store-buildBuild or refresh a knowledge store with knowledge-store-builder — run the pipeline stages, and write the layers that need an LLM (community summaries, topic briefs). Use when the user wants to create a knowledge store, refresh one after code changes, add repositories to an estate, or fill in missing
knowledge-store-exportUse when a knowledge-store finding needs to leave the conversation — attached to a ticket, sent to a data-protection or security owner, or handed to a team that will act on it. Produces a dated, self-contained markdown export with evidence, provenance and honest limits, and keeps sensitive values ou
knowledge-storeAnswer questions from a committed knowledge store built by knowledge-store-builder — architecture, duplication, dependencies, user journeys, business intent, "which repo does X", "why does this exist" — through the knowledge-store MCP server's tools. Use whenever the working directory contains graph
Problems found in this repo's manifests
- .claude-plugin/marketplace.json is not valid JSON
Maintain knowledge-store?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.