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.9 KiB
2.9 KiB
name, description
| name | description |
|---|---|
| roadmap-planning | Plan features and break down work into implementable issues. Use when planning a feature, creating a roadmap, breaking down large tasks, or when the user needs help organizing work into issues. |
Roadmap Planning
How to plan features and create issues for implementation.
Planning Process
1. Understand the Goal
- What capability or improvement is needed?
- Who benefits and how?
- What's the success criteria?
2. Break Down the Work
- Identify distinct components
- Define boundaries between pieces
- Aim for issues that are:
- Completable in 1-3 focused sessions
- Independently testable
- Clear in scope
3. Identify Dependencies
- Which pieces must come first?
- What can be parallelized?
- Are there external blockers?
4. Create Issues
- Follow issue-writing patterns
- Reference dependencies explicitly
- Use consistent labeling
Breaking Down Features
By Layer
Feature: User Authentication
├── Data layer: User model, password hashing
├── API layer: Login/logout endpoints
├── UI layer: Login form, session display
└── Integration: Connect all layers
By User Story
Feature: Shopping Cart
├── Add item to cart
├── View cart contents
├── Update quantities
├── Remove items
└── Proceed to checkout
By Technical Component
Feature: Real-time Updates
├── WebSocket server setup
├── Client connection handling
├── Message protocol
├── Reconnection logic
└── Integration tests
Issue Ordering
Dependency Chain
Create issues in implementation order:
- Foundation (models, types, interfaces)
- Core logic (business rules)
- Integration (connecting pieces)
- Polish (error handling, edge cases)
Reference Pattern
In issue descriptions:
## Dependencies
- Depends on #12 (user model)
- Depends on #13 (API setup)
After creating issues, formally link dependencies:
tea issues deps add <issue> <blocker>
tea issues deps add 14 12 # Issue #14 depends on #12
tea issues deps add 14 13 # Issue #14 depends on #13
Creating Issues
Use the gitea skill for issue operations.
Single Issue
Create with a descriptive title and structured body:
- Summary section
- Acceptance criteria (testable checkboxes)
- Dependencies section referencing blocking issues
Batch Creation
When creating multiple related issues:
- Plan all issues first
- Create in dependency order
- Update earlier issues with forward references
Roadmap View
To see current roadmap:
- List open issues using the gitea skill
- Group by labels/milestones
- Identify blocked vs ready issues
- Prioritize based on dependencies and value
Planning Questions
Before creating issues, answer:
- "What's the minimum viable version?"
- "What can we defer?"
- "What are the riskiest parts?"
- "How will we validate each piece?"