Build documentation and ensure all doc-related checks pass. Use after writing code, before committing.
Load dev/documentation.md for detailed guidance on docstrings and markdown
formatting.
Run make doc
If spell check fails: add new terms to project-words.txt (do NOT sort it)
If new module was created: ensure docs/api/ entry AND mkdocs.yml nav
updated
Repeat until make doc passes
## Documentation Results
- `make doc`: PASS/FAIL
- New terms added to project-words.txt: <list or "none">
- New modules documented: <list or "none">
### Lessons Learned
<Patterns discovered while fixing doc issues — things future agents should know>
<If none, write "None">
Always include Lessons Learned, even if empty. When running as a sub-agent, the main agent needs this for the PR description.
Examples of lessons learned:
docs/api/<module>.md AND an entry in mkdocs.yml nav"mkdocstrings syntax ::: module.path to auto-generate from docstrings"make doc passes