namht-documentlisted

# Spec Document — business ↔ code field-level documentation A native port of Auto Spec extension's `/document`. Produce accurate, citable documentation that a mixed business+technical audience can trust. Use ONLY the provided context (KB + real source); if something isn't there, write `(not found in codebase)` — never invent. **Dual audience:** the document must work for BOTH a non-technical reader (founder / PM / ops) and an engineer. Lead with plain language, then go precise. A non-tech reader should fully grasp the top sections without any background; an engineer gets exact names/types/rules below. Define every unavoidable technical term (inline the first time, and in the closing glossary). ## Input The topic to document (a feature, entity/model, or module). ## Gather context 1. Load relevant `knowledge-base/` docs plus, by default, the business/domain/architecture docs and any matching `knowledge-base/modules/<module>.md`. 2. Discover and read the **relevant source files** for field-level grounding — you must name real classes, functions, and fields. Use Grep/Glob/Read to find them and follow the call paths. ## Output structure (Markdown; use TABLES for every mapping) ``` # <Clear document title> _Scope: <topic> · generated by namht Kit_ ## 0. In plain words (for everyone) 2–4 sentences, zero jargon: what this is, who uses it, why it matters — with an analogy if it helps. A non-technical reader should "get it" from this section alone. ## 1. Business Overview