Generated content is scoped to its audience
acceptednot accepted
User-facing output — release notes, user docs, changelogs — includes only what that audience touches; the audience filter is specced into the task's DoD.
On this page
- Author
- agent
- Created
- Updated
- Review
- not shown
- targets
- groom/draft-plan
- brief
- For user-facing content (release notes, docs, changelogs), put the audience filter into the task's DoD: only what that audience touches, no internal churn.
Rule§
When a plan produces user-facing content (release notes, user docs, changelogs), the content includes only what its audience interacts with; internal churn — CLI internals, build plumbing, refactors the audience never touches — is left out. Audience scoping is decided at generation time and written into the task's DoD, not cleaned up in a post-edit.
Follows from§
- Minimal effective context — a reader
gets only what they touch. In the retro on CLI logging and agent namespacing, generated release notes listed internal
boopingCLI changes users never invoke; the same oversharing recurred in a docs review.