From 25e57b2325f6b81d769d1223ee8abf0a4ef3a7b1 Mon Sep 17 00:00:00 2001 From: Durable Workflow Date: Tue, 20 Oct 2026 08:17:38 +0000 Subject: [PATCH] Require product assessment when resolving documentation gaps --- AGENTS.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 9dc12cf..4996ea1 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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