create-diagramlisted

# Create Diagram Grill to a shared model, plan the diagram, then build through the bundled template and validators. Default to `narrative-architecture` for mixed stakeholder, developer, and manager audiences unless the user explicitly asks for `exact-code-graph` or `executive-concept-map`. ## Workflow 1. **Explore** - Inspect the repo before asking questions the environment can answer: docs, entrypoints, manifests, schemas, tests, routes, pipelines, generated artifacts, and existing diagrams. - Separate discovered facts from inferences when summarizing what you found. 2. **Question** - Read [question-framework.md](references/question-framework.md). - Maintain a temporary request-to-evidence gap ledger and ask only questions that cannot be answered from repo inspection or prior user context. - Ask up to three related blocking questions per round. Cite the request and repository evidence, explain why the answer changes the diagram, present two to four options when feasible, and recommend one with trade-offs. - Incorporate answers, re-explore changed boundaries, and repeat. Do not move to planning until purpose, audience, output location, entities, relationships, omissions, evidence policy, and verification path are known and the resolved model is explicitly confirmed. 3. **Plan** - Read [html-output-guide.md](references/html-output-guide.md) for node type taxonomy, edge types, metadata schema, and builder payload shape. - Ask the user where to creat