Help with sprint planning, backlog grooming, and board organization using Scrumban methodology. Use for prioritization, WIP management, and workflow optimization.
From trellonpx claudepluginhub ramirez-justin/claude-plugins --plugin trelloThis skill is limited to using the following tools:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Integrates PayPal payments with express checkout, subscriptions, refunds, and IPN. Includes JS SDK for frontend buttons and Python REST API for backend capture.
Expert assistance for managing your Trello board using Scrumban methodology - combining the best of Scrum and Kanban.
This skill complements the superpowers workflow skills:
| Superpowers Skill | How It Relates to Board Planning |
|---|---|
writing-plans | Creates implementation plans → convert to Trello cards |
executing-plans | Works through plan steps → track progress on board |
dispatching-parallel-agents | Parallel work streams → visualize as board columns |
finishing-a-development-branch | Completion workflow → move cards to Done |
Workflow example:
brainstorming to design a featurewriting-plans to create implementation stepsexecuting-plans while updating card statusfinishing-a-development-branch and move card to DoneScrumban combines:
Done | Blocked | In-Progress | Next Up | Backlog
Why right-to-left? Work flows from Backlog → Done, and Done should be most visible as a motivator.
Backlog
Next Up
In-Progress
Blocked
Done
| Team Size | In-Progress Limit |
|---|---|
| 1 person | 2-3 cards |
| 2 people | 3-4 cards |
| 3 people | 4-6 cards |
| 5 people | 6-8 cards |
1. Check Blocked column - any items to unblock?
2. Check In-Progress - any items close to done?
3. Pull from Next Up if capacity allows
4. Quick standup questions:
- What did I finish?
- What am I working on?
- Any blockers?
1. Review Done column - archive completed items
2. Celebrate wins!
3. Groom Backlog:
- Remove outdated items
- Break down large items
- Add new items
4. Prioritize Next Up:
- Ensure 5-10 items ready
- Order by priority
5. Check metrics:
- Items completed
- Average time in each column
- Blocked time
1. Retrospective:
- What went well?
- What could improve?
- Action items
2. Process improvements:
- Adjust WIP limits
- Update column definitions
- Add/remove columns
3. Long-term planning:
- Major features coming up
- Technical debt to address
- Learning goals
Must Have (Critical)
Should Have (Important)
Could Have (Nice to Have)
Won't Have (Not Now)
For each item, score:
Formula: (BV + TC + RR) / Size = Priority Score
Higher score = Higher priority
Problem: WIP limit exceeded, nothing getting done
Solution:
1. STOP starting new work
2. Focus on finishing oldest items
3. Help teammates complete their work
4. Don't pull from Next Up until under limit
Prevention:
- Enforce WIP limits strictly
- Make "finishing" the priority
- Daily check on In-Progress count
Problem: Blocked column growing, work stuck
Solution:
1. Daily review of blocked items
2. Escalate blockers immediately
3. Can we work around it temporarily?
4. Is there dependency we can remove?
Prevention:
- Identify dependencies before starting
- Have backup work ready
- Regular communication with dependencies
Problem: Backlog has 100+ items, overwhelming
Solution:
1. Archive items older than 3 months
2. Combine similar items
3. Delete "nice to have" that won't happen
4. Set maximum backlog size (e.g., 50 items)
Prevention:
- Monthly backlog grooming
- Say "no" to low-priority items
- Time-box backlog review
Problem: Finished work, nothing ready to start
Solution:
1. Pull from Backlog immediately
2. Quick prioritization session
3. Pick highest-impact items
4. Ensure they're ready to work on
Prevention:
- Keep 5-10 items in Next Up
- Weekly refill from Backlog
- Flag items that need clarification
By Feature Area
"User authentication" becomes:
- Login page UI
- Password validation
- OAuth integration
- Password reset flow
- Session management
By User Story
"Admin dashboard" becomes:
- Admin can view user list
- Admin can edit user details
- Admin can deactivate users
- Admin can view analytics
By Technical Layer
"API for orders" becomes:
- Database schema for orders
- Order service logic
- REST API endpoints
- API documentation
- Integration tests
By Iteration
"Search functionality" becomes:
- v1: Basic text search
- v2: Filters and sorting
- v3: Advanced search syntax
- v4: Search suggestions
Time from card creation to Done
Good: Days Warning: Weeks Problem: Months
Time from In-Progress to Done
Goal: Minimize this Track: Weekly average
Cards completed per week
Track: Trend over time Goal: Steady or increasing
How long items sit In-Progress
Warning: Items older than 3 days Action: Focus on finishing or move to Blocked
When planning your board, I will:
Review current state:
Suggest actions:
Facilitate planning:
Track progress:
You: "Help me plan what to work on this week"
Me: "Let me review your board first..."
/trello-lists --with-cards
"Here's your current board state:
In-Progress (3 cards) - At WIP limit
Blocked (1 card)
Next Up (4 cards)
Backlog (12 cards)
Recommendations:
Finish first: The API documentation has been in progress for 5 days. Let's either finish it or identify what's blocking it.
Check the blocker: Payment integration has been blocked. Is there an update on Stripe approval?
This week's focus: After finishing current work, I'd suggest:
Backlog grooming needed: You have 12 items in backlog. Want me to help prioritize?
What would you like to focus on?"