mkdocs-initlisted

# Docs Init Generate initial project documentation from codebase analysis. **Scope:** Creates `docs/` from scratch. For updating existing docs → `mk:document-release`. > Also run `mk:project-context` to generate the agent-constitution file (`docs/project-context.md`). `mk:docs-init` generates the full documentation suite; `mk:project-context` generates only the constitution. ## When to Use - Project has no `docs/` directory - `docs/` exists but is empty or has only stubs - User asks to "initialize docs", "create documentation", "generate docs" - After `mk:bootstrap` completes (new project needs docs) Do NOT invoke when: docs already exist and need updating (use `mk:document-release`). ## Process 1. **Check existing state** — does `docs/` exist? Are files already populated? - If populated docs exist → suggest `mk:document-release` instead, stop. 2. **Scout codebase** — activate `mk:scout` to analyze project structure. Skip: `.claude/`, `.git/`, `node_modules/`, `__pycache__/`, `dist/`, `build/` 3. **Merge findings** — consolidate scout reports into context for doc generation 4. **Generate docs** — spawn `documenter` subagent via Task tool with scout context. Output files (adapt to what the project actually has): - `README.md` — project overview (≤300 lines) - `docs/project-overview.md` — what this project is, who it's for - `docs/codebase-summary.md` — directory map, key modules, entry points - `docs/code-standards.md` — conventions found in codeba