Context Engineering Protocol

[](https://github.com/linkpranay-ai/context-engineering-protocol/actions/workflows/ci.yml) [](LICENSE) [](https://github.com/linkpranay-ai/context-engineering-protocol/releases/tag/v0.5.0)

**[Concept](CONCEPT.md) · [Protocol](PROTOCOL.md) · [Glossary](GLOSSARY.md) · [Conformance](CONFORMANCE.md) · [Quickstart](#quickstart) · [Skills](#skills-in-this-repo) · [Runtime support](#runtime-support) · [Evidence](EVIDENCE.md) · [Roadmap](ROADMAP.md) · [Evidence methodology](EVIDENCE-METHODOLOGY.md) · [FAQ](FAQ.md) · [Contributing](CONTRIBUTING.md)**

**New here? Start with [`CONCEPT.md`](CONCEPT.md)** — the conceptual model CEP is built on, written to be read *before* the protocol specification below.

Don't let the agent guess what's true. Make it prove the context agrees, then get a human to sign off before it writes a line of code.

A set of AI-coding-agent skills that assemble a **human-approved, source-attributed context package** — code graph + requirements + org conventions + constraints — before a generation task runs, instead of letting the agent free-read the repo and guess.

**In practice:** an ungrounded assistant invented the same hallucinated concept twice, in two completely unrelated codebases — a UI framework and a telecom protocol stack. The CEP-grounded run produced 26 real, checkable citations and zero inventions across both. See [Evidence](EVIDENCE.md) for the full measured breakdown, plus field-validated runs across Claude Code, GitHub Copilo