Hugo Nijhuis
1c0b6b3712
Updated skills and commands to identify and formally link issue dependencies using tea CLI: Skills updated: - issue-writing: Document deps in description + link with tea CLI - backlog-grooming: Check for formal dependency links in checklist - roadmap-planning: Link dependencies after creating issues Commands updated: - create-issue: Ask about and link dependencies for new issues - plan-issues: Create in dependency order, link with tea issues deps add - groom: Check dependency status, suggest missing links 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
name, description
| name | description |
|---|---|
| backlog-grooming | Review and improve existing issues for clarity and actionability. Use when grooming the backlog, reviewing issue quality, cleaning up stale issues, or when the user wants to improve existing issues. |
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 in description
- Dependencies formally linked (
tea issues deps list <number>) - No circular dependencies
- Blocking issues are tracked
To check/fix dependencies:
tea issues deps list <number> # View current dependencies
tea issues deps add <issue> <blocker> # Add missing dependency
tea issues deps remove <issue> <dep> # Remove incorrect dependency
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