# Backlog Grooming How to review and improve existing issues. ## Grooming Checklist For each issue, verify: ### 1. Title Clarity - [ ] Starts with action verb - [ ] Specific and descriptive - [ ] Understandable without reading description ### 2. Description Quality - [ ] Has clear summary - [ ] Explains the "why" - [ ] Provides enough context ### 3. Acceptance Criteria - [ ] Criteria exist - [ ] Each criterion is testable - [ ] Criteria are specific (not vague) - [ ] Complete set (nothing missing) ### 4. Scope - [ ] Not too broad (can complete in reasonable time) - [ ] Not too narrow (meaningful unit of work) - [ ] Clear boundaries (what's included/excluded) ### 5. Dependencies - [ ] Dependencies identified - [ ] No circular dependencies - [ ] Blocking issues are tracked ### 6. Labels - [ ] Type label (bug/feature/etc) - [ ] Priority if applicable - [ ] Component labels if applicable ## Common Issues to Fix ### Vague Titles - Bad: "Fix bug" - Good: "Fix login form validation on empty email" ### Missing Acceptance Criteria Add specific, testable criteria based on the description. ### Scope Creep If issue covers multiple features, split into separate issues. ### Stale Issues - Close if no longer relevant - Update if context has changed - Add "needs-triage" label if unclear ### Duplicate Issues - Close duplicate with reference to original - Merge relevant details into original ## Grooming Workflow 1. **Fetch open issues**: `fj issue search -s open` 2. **Review each issue** against checklist 3. **Improve or flag** issues that need work 4. **Update issue** with improvements: `fj issue edit --body "..."` 5. **Add labels** as needed: `fj issue label add