en-quire

Skill: en-quire — Markdown Document Management

Purpose: Instructions for agents using en-quire MCP tools to read, search, edit, and manage markdown and YAML documents.

---

Orientation: Multi-Root and doc_status

en-quire manages documents across multiple roots — separate directories for different document types (e.g. codex, agents, skills, testing). Each root can have its own git configuration and governance model.

Start every session with:

1. doc_status — see all configured roots, their git status, index health, and pending proposals
2. doc_list — see all files, or scope to a specific root with doc_list(scope: "skills")

File paths include the root prefix: codex/en-quire.mdx, agents/researcher.md, skills/en-quire/SKILL.md. Use the prefix in all tool calls.

Search works across all roots by default. Scope to a single root with doc_search(query: "...", scope: "agents").

When to Use en-quire

Use en-quire tools (doc_*) instead of filesystem tools (read_file, write_file, edit_file) for any operation on:

• Markdown files (.md, .mdx) — SOPs, skill files, codex articles, session memory, agent profiles
• YAML files (.yaml, .yml) — Docker Compose, config files, CI/CD pipelines, Kubernetes manifests

en-quire provides section-level addressing, structural search, and diff responses that eliminate the need to read or rewrite whole files. For YAML, "sections" are key paths (e.g. services.api.environment).

Use filesystem tools only when:

• You are working with file types en-quire doesn't support (JSON, JS, etc.)
• You need to move or copy files between directories or roots

Core Workflow: Outline → Read → Edit

Every interaction with a document follows this sequence:

1. doc_outline — Get the structure first. This is non-negotiable. Never read a whole file to orient yourself. For markdown, this returns the heading tree. For YAML, it returns the key hierarchy with value types.
2. doc_read_section — Read only the section you need. Use the heading text (markdown) or dot-path (YAML, e.g. services.api.environment). Take the address straight from the doc_outline result — a heading address must match the heading text exactly, including any trailing qualifier or parenthetical, so copy it rather than retyping from memory or from how the body prose refers to a section (e.g. "§13.1 Storage Mapping").
3. Edit with the right tool:
   • doc_set_value — change a single value (YAML scalar or markdown section body). The simplest edit tool — one path, one value.
   • doc_replace_section — rewrite a block's content (mapping values in YAML, section body in markdown)
   • doc_append_section — add content to the end of a section (table rows, list items, new YAML keys)
   • doc_find_replace — change a term or phrase across the whole document
   • doc_insert_section — add a new section before or after an existing one
   • doc_delete_section — remove a section entirely
   • doc_move_section — atomically delete a section from its current location and insert it at a new position (cut-and-paste). Heading levels adjust automatically including all children. Use this instead of separate delete + insert calls.
   • doc_generate_toc — generate or update a table of contents from the heading structure