Hugo Nijhuis
68675a7e12
- Replace fj CLI with tea CLI across all commands - Create new gitea skill, remove forgejo skill - Update all agents to use gitea skill - Update commands to use skill-based approach (reference skills instead of embedding CLI commands) - Update all documentation (README, ARCHITECTURE, VISION, writing guides) - Swap git remotes: origin now points to git.flowmade.one (Gitea) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
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
Use the gitea skill for issue operations.
- Fetch open issues
- Review each issue against checklist
- Improve or flag issues that need work
- Update issue with improvements
- Add labels as needed
Questions to Ask
When grooming, consider:
- "Could a developer start work on this today?"
- "How will we know when this is done?"
- "Is the scope clear?"
- "Are dependencies explicit?"
Batch Grooming
When grooming multiple issues:
- List all open issues
- Categorize by quality (ready, needs-work, stale)
- Focus on "needs-work" issues
- Present summary of changes made