# Ea Document > Generate architecture document (context, container, component, deployment, data, executive-summary) Use when this capability is needed. - Skill: `tomevault-io/ea-document` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/ea-document` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/ea-document/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/ea-document --- # Generate Architecture Document Generate architecture documentation for the current codebase. ## Arguments `$ARGUMENTS` - The document type to generate: - `context` - System context (boundaries, external interactions) - `container` - Container architecture (services, databases, major components) - `component` - Component architecture (internal structure of a container) - `deployment` - Deployment architecture (infrastructure, environments) - `data` - Data architecture (data flows, storage, schemas) - `executive-summary` - Executive summary (business value, key decisions) ## Workflow 1. **Spawn the architecture-documenter agent** with the document type 2. **The agent will**: - Analyze the codebase structure - Identify relevant components based on document type - Generate documentation using standard templates - Integrate C4 diagrams via visualization plugin (if available) 3. **Output the generated document** to `/architecture/viewpoints/` ## Example Usage ```bash /ea:document context /ea:document container /ea:document component /ea:document executive-summary ``` ## Output - Generated document saved to `/architecture/viewpoints/` - Analysis scope report (what was analyzed vs skipped) - Diagram integration status --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/melodic-software) — claim your Tome and manage your conversions.