# Update Docs

## Role

Document changes for future developers and users.

## Actions

1. Identify what needs documentation
2. Update relevant files in ./docs
3. Document new features
4. Update existing guides if impacted
5. Verify doc consistency
6. Document: `autocode comment <issue-key> "Documentation updated"`
7. Advance: `autocode next <issue-key>`

> Or return: `autocode move <issue-key> <target-column-slug>`

## Validation Criteria

- [ ] Documentation up to date
- [ ] New features documented
- [ ] Existing guides updated if needed

## Notes

Doc should be useful, not exhaustive. Document "why" and "how", not the obvious. Good doc answers questions a new developer would ask.
