Add dependency management to issue workflows

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>
This commit is contained in:
2026-01-07 16:35:39 +01:00
parent f50b0dacf3
commit 1c0b6b3712
6 changed files with 55 additions and 21 deletions

View File

@@ -11,23 +11,27 @@ argument-hint: [issue-number]
## If issue number provided ($1):
1. **Fetch the issue** details
2. **Evaluate** against grooming checklist
3. **Suggest improvements** for:
1. **Fetch the issue** details with `tea issues <number> --comments`
2. **Check dependencies** with `tea issues deps list <number>`
3. **Evaluate** against grooming checklist
4. **Suggest improvements** for:
- Title clarity
- Description completeness
- Acceptance criteria quality
- Scope definition
4. **Ask user** if they want to apply changes
5. **Update issue** if approved
- Missing or incorrect dependencies
5. **Ask user** if they want to apply changes
6. **Update issue** if approved
7. **Link/unlink dependencies** if needed: `tea issues deps add/remove <issue> <dep>`
## If no argument (groom all):
1. **List open issues**
2. **Review each** against grooming checklist
2. **Review each** against grooming checklist (including dependencies)
3. **Categorize**:
- Ready: Well-defined, can start work
- Needs work: Missing info or unclear
- Ready: Well-defined, dependencies linked, can start work
- Blocked: Has unresolved dependencies
- Needs work: Missing info, unclear, or missing dependency links
- Stale: No longer relevant
4. **Present summary** table
5. **Offer to improve** issues that need work
4. **Present summary** table with dependency status
5. **Offer to improve** issues that need work (including linking dependencies)