context-document

# context ## When to use Use this skill when: - Documenting a module, service, or integration for future reference - Exploring an unfamiliar area of the codebase - Preparing for a feature that touches multiple areas - Onboarding to a new part of the codebase Do NOT use when: - Writing code or features - Creating roadmaps (use `roadmap-management` skill) ## Procedure: Manage contexts 1. **Identify scope** — Which area of the codebase needs a context document? 2. **Research** — Use codebase-retrieval to understand the area (files, patterns, dependencies). 3. **Write or update** — Create/update the context doc following the template below. 4. **Verify** — Confirm all referenced files exist and descriptions match current code. A **context document** is a structured snapshot of a codebase area: - What it does, why it exists - Key files, classes, and patterns - Database tables and API endpoints - Dependencies and known issues Unlike feature plans (future-focused) or roadmaps (task-focused), contexts are **present-focused** — they describe the current state of the code. ## File structure ``` .augment/contexts/ # Shared contexts (about the agent system itself) ├── augment-infrastructure.md ├── skills-and-commands.md └── documentation-hierarchy.md agents/settings/contexts/ # Project-wide contexts ├── {context-name}.md {module_root}/{Module}/{agent_folder}/settings/contexts/ # Module-scoped contexts ├── {context-name}.md ...