# Use the docs with coding agents

Give an agent a small, versioned source set and keep documentation lookup separate from action authority.

Source context: Source-guided
Source: https://github.com/lssm-tech/contractspec/blob/d58fa5b7de53a947811e5cc68346be028ce18528/packages/platform/delivery/cli-runtime/src/authoring-mcp/docsMcp.tools.ts

## Start with a focused context packet

Give the agent the task, selected package versions or source commit, the relevant guide, and the exact contract or runtime reference. A small coherent source set is easier to verify than the entire monorepo corpus.

Ask it to identify which behavior is declared, which code implements it and which host dependency supplies authority. This encourages it to preserve the same boundaries a human reviewer would inspect.

## Choose the smallest useful entry point

This review site offers an area index, a complete package index and a bounded agent overview for every package. Start with the overview, then read the relevant package manual or structured source data. Package and area evidence is pinned to bcc79fcc; the MCP source discussed below retains its stated d58fa5b7 context.

The Copy agent overview control provides purpose, source identity, declared capabilities and a limited import selection, with links to deeper evidence. Full Markdown and JSON remain available when the task needs them. Package presence, a version string and a declared import do not establish registry availability or successful execution.

| Need | Entry point in this review | What to inspect |
| --- | --- | --- |
| Orientation | /llms.txt | Choose a core guide, area or package |
| All packages | /docs/packages/index.json | Exact package identity and retrieval locations |
| One package, bounded context | /docs/packages/[slug].context.md | Source pin, purpose, runtime and selected imports |
| Full package evidence | /docs/packages/[slug].md or .json | README, capabilities, targets, dependencies and scripts |
| Area relationships | /docs/areas/index.json | Entry points and related technical areas |

## Understand the lookup tools

The inspected authoring MCP source defines documentation search, get, route resolution, contract lookup and facet listing. These are documentation operations. Their presence in source is not a claim that a public hosted MCP endpoint has been qualified.

Documentation lookup does not authorize editing a repository, executing a provider action or deploying an application. Keep the agent's work permissions separate from the information it can read.

A plugin, MCP server or skill should retrieve the same versioned documentation records and keep task instructions separate from retrieved evidence. This static review supplies the web, Markdown and JSON projections; the proposed shared DocSpec compiler and retrieval service are described in the [DocSpec architecture review](https://lssm.co/). It does not expose a new MCP endpoint or install a coding-agent skill.

## Review the generated answer

Require links to the exact sources behind proposed APIs or commands. Check that examples use the same release channel, and ask for an explicit statement when a snippet is illustrative rather than executed.

For an implementation task, verify the result through the owning source checks and a meaningful runtime case. A confident answer that quotes documentation is still a proposal until the relevant behavior is tested.