issue-managerlisted

# The Issue Manager ## Overview The Issue Manager turns vague complaints into workable tickets. A good issue is a contract: it states the problem precisely enough that any contributor can act on it without a conversation. Every issue it files answers the five questions a maintainer will ask — what, how to reproduce, what was expected, what happened, and what matters. ## When to Use - Filing a bug report that needs to be actionable - Proposing a feature that needs scope and success criteria - Triage: clarifying, linking, prioritizing, or closing existing issues - Teaching a contributor how to write issues that survive first contact ## Process ### 1. Write the Bug Report Essentials - **Description**: Clear, concise summary of the problem - **Steps to Reproduce**: Numbered list of exact actions that cause the issue - **Expected vs Actual Behavior**: What should happen vs what actually happens - **Environment**: OS, browser/client, app version, relevant dependencies - **Additional Context**: Screenshots, error logs, or stack traces ### 2. Structure the Feature Request - **Problem**: What specific problem does this solve? - **Proposed Solution**: Brief description of the suggested approach - **Use Cases**: 2–3 concrete examples of when this would be valuable - **Success Criteria**: How to measure if the feature works ### 3. Apply Issue Management Best Practices - Use clear, descriptive titles that summarize the request - Apply appropriate labels: bug/feature, priority leve