chore: Update generic issue template

Author: Terraform

.github/ISSUE_TEMPLATE/1-generic-issue.md

@@ -7,25 +7,81 @@ assignees: ''
 
 ---
 
+<!--
+How to fill out this template:
+
+1. Describe outcomes, not implementation. Explain WHAT should happen and WHY,
+   not HOW to build it. Implementation details belong in a PR, not in an issue.
+2. Acceptance Criteria MUST use GitHub checkboxes (`- [ ] ...`), not plain
+   bullets (`- ...`). Plain bullets are not parsed as tasks by GitHub or by
+   automation/AI tools and will be missed during triage.
+3. Keep every section. If a section does not apply, write `N/A` as its body.
+   Do not delete sections and do not leave placeholder text.
+4. Delete every HTML comment (including this one) as you fill in the sections.
+   Comments are guidance for the writer and should not remain in the submitted
+   issue.
+-->
+
 ## Description
 
-Description of the problem, with any relevant context to better understand the issue.
+<!--
+What is the problem or request, and why does it matter? Include any context
+a reader needs to understand the issue without prior knowledge. Avoid jumping
+to a solution here — describe the problem first.
+
+Delete this comment when you fill in the section.
+-->
 
 ## Expected Behavior or Outcome
 
-- Key requirements and specifications.
+<!--
+The user-visible behavior or outcome once this is resolved. Phrase as
+observable results ("the command exits with code 0", "the page renders X"),
+not as code changes ("we add a foo() function").
+
+Use either a bulleted list or a short narrative paragraph — whichever fits
+the issue best.
+
+Delete this comment when you fill in the section.
+-->
+
+- Listed item, or use the narrative style
 
 ## Acceptance Criteria
 
-- Criteria for acceptance and success.
-- Optional section
+<!--
+Concrete, verifiable conditions that must be true to consider this issue done.
+
+REQUIRED FORMAT: each criterion MUST be a GitHub checkbox so it is tracked as
+a task by GitHub, automations, and AI agents:
+
+    - [ ] The CLI exits with code 0 when the input file is valid.
+    - [ ] An error message is shown when the file is missing.
+
+Do NOT use plain bullets (`- ...`) — they will not be picked up as tasks.
+
+Focus on outcomes ("the user sees X"), not on implementation ("we add a
+foo() function"). If criteria can't be defined yet, write `N/A`.
+
+Delete this comment when you fill in the section.
+-->
+
+- [ ] 
 
 ## Resources/References
 
-- Links to relevant documentation or tools.
-- Optional section
+<!--
+Links to relevant docs, tools, dashboards, related issues, or prior
+discussions. Write `N/A` if there are none.
+
+Delete this comment when you fill in the section.
+-->
 
 ## Notes
 
-- Any additional information or context.
-- Optional section
+<!--
+Any additional context that doesn't fit above. Write `N/A` if there is
+nothing to add.
+
+Delete this comment when you fill in the section.
+-->