Skip to content

Assess documentation gaps as product feedback #214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rmcdaniel merged 1 commit into from
Oct 20, 2026
Merged

Assess documentation gaps as product feedback #214

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,12 @@ but they must not replace these project-wide rules.
- Feedback is evidence. Product judgment determines the underlying need,
priority, scope, and solution; neither an issue label nor submitted prose
overrides that judgment.
- Review documentation gaps as product feedback. Decide whether the right fix
is clearer documentation, a product bug fix, or a new capability, based on
the user's need and the product contract. Record the decision and any linked
implementation work in the owning issue. Describe current limitations
honestly while that work is pending; documenting a workaround does not
complete an accepted product requirement.
- Keep moving from one concrete product action to the next until the current
objective is complete, a human explicitly stops the work, or a genuinely
external decision is required. Do not stop at a status update when an allowed
Expand Down
Loading