Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From trello
Create well-structured Trello cards from code changes, conversations, or requirements. Use when creating cards, bugs, features, or tasks. Analyzes context to generate clear titles, descriptions, checklists, and appropriate placement in the Scrumban workflow.
npx claudepluginhub ramirez-justin/claude-plugins --plugin trelloHow this skill is triggered — by the user, by Claude, or both
Slash command
/trello:card-creationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Expert assistance for creating well-structured, comprehensive Trello cards from any context.
Writes high-quality product tickets including user stories, bugs, improvements, spikes, and technical debt for Jira, Linear, Notion, GitHub Issues, or Markdown. Use to create, refine, split, or review tickets.
Task creation for issue trackers — structured descriptions, acceptance criteria, field categorization, and tracker linking. Invoke whenever task involves creating work items in any issue tracker — bugs, features, stories, tasks, or any tracked work from standalone requests or decomposition documents.
Interactively writes structured tickets (story, bug, epic, initiative, subtask, issue) with type-specific fields and quality checks. Outputs clean Markdown ready for any tracker.
Share bugs, ideas, or general feedback.
Expert assistance for creating well-structured, comprehensive Trello cards from any context.
This skill complements the superpowers workflow skills. Use superpowers skills first for process guidance, then this skill for Trello execution:
| Situation | Use Superpowers First | Then Use This Skill |
|---|---|---|
| New feature idea | brainstorming → explore & design | Create Feature card |
| Bug discovered | systematic-debugging → find root cause | Create Bug card |
| Planning work | writing-plans → break down tasks | Create cards for each step |
| Work completed | finishing-a-development-branch → verify | Move card to Done |
Key principle: Superpowers handles the how (methodology), this plugin handles the where (Trello tracking).
When to use: Something is broken or not working as expected
Card structure:
Example:
Title: Login fails when email contains + character
Description:
## Problem
Users cannot log in if their email contains a + character.
## Steps to Reproduce
1. Go to login page
2. Enter email with + (e.g., user+test@example.com)
3. Enter valid password
4. Click submit
## Expected
User logs in successfully
## Actual
Error: "Invalid email format"
## Impact
Affects users with email aliases (common in tech)
Checklist:
[ ] Fix email validation regex
[ ] Add unit test for + in emails
[ ] Test with various email formats
[ ] Verify in staging
When to use: New functionality or capability
Card structure:
Example:
Title: Add dark mode toggle to settings
Description:
## User Story
As a user, I want to toggle dark mode so that I can reduce eye strain at night.
## Requirements
- Toggle in settings page
- Persists across sessions
- Smooth transition animation
- Respects system preference as default
## Acceptance Criteria
- [ ] Toggle visible in settings
- [ ] Theme changes immediately
- [ ] Preference saved to localStorage
- [ ] Respects prefers-color-scheme
- [ ] All components support both themes
Checklist:
[ ] Create theme context
[ ] Add toggle component
[ ] Update CSS variables
[ ] Test all components
[ ] Add to settings page
When to use: Technical work, refactoring, maintenance
Card structure:
Example:
Title: Refactor authentication module for testability
Description:
## Objective
Make the auth module easier to test by extracting dependencies.
## Approach
1. Extract HTTP client as dependency
2. Create interfaces for external services
3. Add dependency injection
4. Update tests to use mocks
## Benefits
- Faster tests (no network calls)
- Easier to test edge cases
- Better separation of concerns
Checklist:
[ ] Extract HTTP client interface
[ ] Update AuthService constructor
[ ] Create mock implementations
[ ] Update existing tests
[ ] Add new edge case tests
When creating a card based on code I've written or changes I've detected:
Analyze the change:
Determine card type:
Extract details:
Generate structured content:
[ ] Implement core functionality
[ ] Add unit tests
[ ] Add integration tests
[ ] Update documentation
[ ] Code review
[ ] Test in staging
[ ] Reproduce the bug
[ ] Identify root cause
[ ] Implement fix
[ ] Add regression test
[ ] Verify fix works
[ ] Check for similar issues
[ ] Code follows style guide
[ ] Tests pass
[ ] No security vulnerabilities
[ ] Performance is acceptable
[ ] Documentation updated
## Problem
[Brief description of what's broken]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Environment
- Browser: [if applicable]
- OS: [if applicable]
- Version: [app version]
## Screenshots/Logs
[If available]
## Possible Fix
[If you have ideas]
## User Story
As a [user type]
I want [goal]
So that [benefit]
## Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
## Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
## Technical Notes
[Any implementation considerations]
## Out of Scope
[What we're NOT doing]
## Objective
[What needs to be accomplished]
## Context
[Why this work is needed]
## Approach
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Definition of Done
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
When you need to create a card, I will:
/trello-create commandYou: "The authentication module I just wrote should be tracked"
Me: "I'll create a feature card for this. Let me analyze what you built...
Proposed Card:
Title: Implement OAuth 2.0 authentication system
List: Next Up (ready to work on) or In-Progress (if you're working now)
Description:
As a user, I want to login with OAuth providers so I don't need another password.
Files modified:
src/auth/oauth.js - OAuth client integrationsrc/components/login.js - OAuth login buttonssrc/config/auth.js - Provider configurationChecklist:
Does this look good? Should I create it?"
You: "Yes, put it in In-Progress"
Me: [Uses /trello-create] "Created card in In-Progress. Would you like me to assign it to you or add any labels?"