Commit 8e1e11236f79

@@ -243,6 +243,32 @@ Or something else?
 What are your requirements for this feature?
 ```
 
+### Structured Questions with Fast-Path
+
+For multi-question rounds, use numbered questions with lettered options and a compact reply format:
+
+```
+1) Scope?
+   a) Minimal change (default)
+   b) Refactor while touching the area
+   c) Not sure - use default
+
+2) Compatibility target?
+   a) Current project defaults (default)
+   b) Also support older versions: <specify>
+   c) Not sure - use default
+
+Reply with: `defaults` (accept all defaults) or `1a 2b`
+```
+
+Bold the recommended choice. Include a `defaults` fast-path so the user can accept all recommendations at once.
+
+### Anti-Patterns
+
+- Don't ask questions you can answer with a quick, low-risk discovery read (configs, existing patterns, docs)
+- Don't ask open-ended questions if a tight multiple-choice or yes/no would eliminate ambiguity faster
+- Don't ask more than 5 questions at once — if you need more, split into rounds
+
 ### Explore Alternatives Always
 
 Never settle on first approach. Always:

@@ -233,7 +233,57 @@ For tasks/stories:
 
 ## Description Templates
 
-### Bug Template
+### Red Hat Bug Template (Jira Formatting)
+
+When creating bugs for Red Hat Jira (issues.redhat.com), use Jira formatting (not markdown) so it pastes correctly into the Jira textbox:
+
+```
+h3. *Description of problem:*
+
+[What's wrong]
+
+h3. *Workaround (if any):*
+
+[Workaround or "None"]
+
+h3. *Prerequisites (if any, like setup, operators/versions):*
+
+[Setup requirements]
+
+h3. *Steps to Reproduce*
+
+# [First step]
+# [Second step]
+# [Third step]
+
+h3. *Actual results:*
+
+[What happens]
+
+h3. *Expected results:*
+
+[What should happen]
+
+h3. *Reproducibility (Always/Intermittent/Only Once):*
+
+[Frequency]
+
+h3. *Acceptance criteria:*
+
+*Definition of Done:*
+
+[Criteria]
+
+h3. *Build Details:*
+
+[Version, build info]
+
+h3. *Additional info (Such as Logs, Screenshots, etc):*
+
+[Extra context]
+```
+
+### Bug Template (Markdown)
 ```markdown
 ### Description of problem:
 [What's wrong]