change-docs-skill

Run a post-change documentation checklist after every code modification. Check whether the change affects README sections like Architecture, Key Features, or Environment Variables, then update the corresponding docs/ files such as api-reference.md or architecture.md.

Add the feature to the README Key Features list, update the Architecture diagram if components changed, and add an API usage example. If the feature introduces new endpoints or agents, also update docs/api-reference.md or docs/agents-and-tools.md.

Update Cursor skills whenever a code pattern changes, such as sync-to-async conversions, new factories, or agent structure modifications. Outdated skill examples cause the AI to generate incorrect code in future tasks.

Avoid creating new doc files unless a genuinely new area is introduced, rewriting the entire README for minor changes, or documenting internal implementation details in user-facing README sections. Make surgical updates only.

No external dependencies are required. The Skill is a pure instruction set that guides the AI through documentation checks using your existing README.md, docs/ directory, and .cursor/skills/ folder.