spec-documentlisted

# Write a Docs Artifact Maintain the knowledge substrate: add or correct a feature baseline, record a numbered business rule, add a glossary term, update the domain model, or refresh the architecture map. Drafts from code, marked confirmed/inferred; the owner approves. This is the engine the spec lifecycle uses to keep docs in sync (`spec-create`/`spec-close`/`spec-cancel`/`spec-execute` Phase D call into these conventions); it also runs standalone for ad-hoc doc maintenance. ## Resolve location and template Learn from the project (read two sibling docs in the target folder; mimic, don't invent) -> profile (`features_dir` / `rules_dir` / `decisions_dir` / ...) -> ai-first-docs default. The type sets the template (`references/doc-types.md`): - **feature** -> `features/<feature>.md`: what it does TODAY + EARS criteria; business language, no code / types / class-names. - **rule** -> `rules/R-NNN-<slug>.md`: one atomic, numbered, testable business rule, paired 1:1 with a contract test. - **glossary** -> a term in `glossary.md`: one precise meaning, relations to other terms. - **model** -> `model.md`: domain aggregates and invariants. - **architecture** -> `architecture/<...>`: condensed arc42 / dependency-map / golden-path, container/component level. ## Steps 1. **Search first.** A doc for this topic may exist - update it in place, never fork a parallel doc. One concept, one canonical doc. 2. **Read two siblings** to match structure and tone. 3. **Draft from code as ground