grimdevautodocslisted

# AutoDocs ## Purpose Build a small, evolving source-of-truth documentation system that makes future work easier. Keep documentation: - concise - current - audience-neutral - easy to find - safe to share at the repository's intended visibility level Document durable context that code and live tools do not already explain: - why a workflow exists - how to operate it - important constraints - decisions and their consequences - recurring failure modes and prevention notes ## Read Before Writing Before changing documentation: 1. Read the repository's `AGENTS.md`. 2. Read `docs/README.md` when it exists. 3. Read the relevant existing project docs. 4. Inspect the current code or tool state when the documentation depends on it. 5. Find the smallest canonical document that should own the information. Do not create a second source of truth when an appropriate document already exists. ## Suggested Documentation Shell Projects may begin with this small structure and add folders only when needed: ```text AGENTS.md docs/ README.md product/ dev/ ops/ memory/ MEMORY.md ``` Recommended ownership: - `AGENTS.md` — critical instructions and routing that must always be loaded - `docs/README.md` — documentation index and canonical-location map - `docs/product/` — product behavior, decisions, and user-facing constraints - `docs/dev/` — architecture, development workflows, and technical operations - `docs/ops/` — recurring operational procedures and runbooks - `memory/MEMORY.m