docs-discover git:20261018.f44fde5A

Immutable. This exact content never changes and is served at /api/v1/blob/0d623667bf8d3715.

---
name: docs-discover
description: Use when starting documentation work in an unfamiliar codebase or feature; establish readers, source evidence, content ownership, and validation commands.
---

# Discover the documentation contract

1. Resolve the checkout and version. Read repository instructions, contributor rules,
   README, manifests, lockfiles, docs configuration, and CI. Inspect status before edits.
   Register the project through available onboarding tools if needed; honor fences.
2. Identify the reader's task, starting knowledge, environment, and expected result.
   Infer from the request and existing docs; ask only for consequential missing decisions.
   App users may lead an app's navigation; a library may need developer paths first.
3. Inventory entry points, navigation, published and in-app docs, generated pages, and
   existing audit trackers. Identify canonical owners and historical/internal documents.
   Discover the site's actual renderer, base path, link conventions, and asset pipeline.
4. Trace the requested behavior through entry points, configuration, UI/CLI definitions,
   tests, and implementation. Record source paths and commit for factual claims. Resolve
   contradictions against the target version; record uncertainty rather than guessing.
5. Identify exact build, generation, link, test, and preview commands from the repository.
   Do not install arbitrary tools or run production workflows just to explore. Use an
   isolated environment for commands with side effects and respect command approvals.

Done when the working brief identifies audience/outcome, scope, canonical pages,
source evidence, known uncertainties, and required checks. Reuse an existing tracker;
for a small task keep the brief in the working response instead of creating process files.
Then load the relevant writing, audit, structure, or media skill and proceed within scope.