docs-structure-templateslisted

# docs-structure-templates — Structure and Formatting Analysis ## Workflow 1. **Connect to Docsbook** — run `list_workspaces` to find the workspace, then `get_doc_graph` to get all pages with metadata. Offer to create the workspace if not indexed. Reindex if graph is empty or stale. 2. **Read pages** — use `read_doc_sections` to access frontmatter and content structure. Prioritize Tier 1 pages (quick-start, pricing, auth) first. 3. **Apply checklist** — check frontmatter fields, heading hierarchy, prerequisites and setup sections, code blocks, page length/density, and callout usage. 4. **Produce report** — return one JSON issue object per finding, sorted by severity. ## Guardrails - Do not edit any documentation files — surface findings only. - Confirm with the user which frontmatter fields are required for this project (some projects have custom fields beyond `title` and `description`). - A page type determines which sections are required — don't flag a reference page for missing prerequisites. - Do not modify the `docs-content-types` skill's output — classify page type there, not here. ## MCP Tools | Tool | Purpose | |------|---------| | `mcp__docsbook__list_workspaces` | Find workspace | | `mcp__docsbook__get_doc_graph` | Page list with titles and metadata | | `mcp__docsbook__read_doc_sections` | Read frontmatter and heading structure | | `mcp__docsbook__reindex_doc_graph` | Refresh graph if empty or stale | ## Checklist ### Frontmatter - [ ] **`title` present** —