Kibi FAQs

Question 1

What kind of traceability does Kibi provide?

Accepted Answer

Kibi provides end-to-end traceability for requirements, tests, and architectural decisions. You can link code symbols back to their original requirements, see test coverage, understand architectural constraints, and trace dependencies in event-driven systems or feature flags.

Question 2

What are the core components of Kibi?

Accepted Answer

Kibi includes `kibi-core` (Prolog knowledge graph), `kibi-cli` (command-line interface), `kibi-mcp` (Model Context Protocol server for LLMs), `kibi-opencode` (OpenCode plugin), and `kibi-vscode` (VS Code extension).

Question 3

What is Kibi and what does it do?

Accepted Answer

Kibi is a repo-local, per-git-branch, queryable knowledge base for software projects. It stores linked entities like requirements, tests, and architectural decisions, ensuring end-to-end traceability between your code and documentation.

Question 4

How does Kibi enhance AI agents and LLMs?

Accepted Answer

Kibi boosts AI agents' memory by maintaining a living, verifiable project memory. It offers an LLM agent-friendly Model Context Protocol (MCP) server, allowing agents to query and update the knowledge base safely without risking file corruption.

Question 5

How does Kibi handle multiple git branches?

Accepted Answer

Kibi is designed with 'branch-local memory,' meaning every git branch gets its own knowledge base snapshot. This preserves context as you switch between features, ensuring traceability remains intact without polluting other branches.

Kibi

Kibi

Key Features

Use Cases

Key Features

Use Cases