Documentation is part of the Definition of Done
No feature is considered complete until its documentation, user pathway, access rules, limitations, and release notes are updated.
Documentation Update Rule
Every meaningful product change should answer:
- What changed?
- Who can access it?
- Is it public, private, planned, or future?
- What user pathway changed?
- What documentation page needs updating?
- What limitations or safety notes changed?
- Should the changelog be updated?
- Should the feature status table be updated?
- Should testers be notified?
Truthfulness rules
- Do not create fake release history.
- Do not invent shipped features.
- Do not claim features are live unless they are actually implemented.
- Do not mark documentation as current unless it reflects the current product state.
Where updates land
- Changelog — public-safe log of updates.
- Feature Status — public, private, planned, or future.
- Release Notes — longer public-safe write-ups.