osx-maintain-ai-docslisted

Update project documentation after implementing an OpenSpec change. > **Mode** — see `references/osx-mode-conventions.md`. When `OSX_AUTONOMOUS=1` is set, skip interactive confirmation and proceed with reasonable defaults. **Input**: optionally specify a change name. If omitted, infer from conversation context or prompt. --- ## Core Principles | Principle | Application | |-----------|-------------| | **Infer** | Only document what AI can't infer from code | | **Reference, don't embed** | Use progressive disclosure — point at detail, don't inline it | | **Tables over prose** | Token efficiency: tables beat verbose lists | | **Concrete** | Specific commands, not vague instructions | **Target lengths**: - Ideal: <300 lines (~1200 tokens) - Warning: >300 lines (review needed) - Maximum: >500 lines (must split) --- ## Steps ### 1. Select the change If a name is provided, use it. Otherwise: infer from context, auto-select if only one active change exists, or run `openspec list --json` and prompt. Auto-select first candidate under `OSX_AUTONOMOUS=1`. Always announce: "Using change: <name>" and how to override. ### 2. Read change artifacts Read files from `openspec/changes/<name>/`: - `proposal.md` — Intent, scope, new features/capabilities - `specs/` — New requirements, modified behaviors - `design.md` — Architectural decisions, new patterns, file changes - `tasks.md` — Checked items = what was actually built Extract: new commands, components, patterns, APIs/endpoints