Guide for coordinating work across Trello, Jira, and Confluence. Use when work spans multiple tools, when deciding which tool to use, or when linking work items across systems.
From integration-pluginnpx claudepluginhub ramirez-justin/claude-plugins --plugin integrationThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Expert guidance for coordinating work across Trello, Jira, and Confluence.
| Scenario | Tool | Why |
|---|---|---|
| Quick task tracking | Trello | Lightweight, visual, fast |
| Personal/team kanban | Trello | Simple board management |
| Sprint planning | Jira | Story points, velocity, sprints |
| Bug tracking with SLAs | Jira | Workflows, priorities, reporting |
| Complex project management | Jira | Dependencies, epics, roadmaps |
| Meeting notes | Confluence | Rich text, collaboration |
| Technical documentation | Confluence | Structured, searchable |
| Decision records (ADRs) | Confluence | Permanent, linkable |
| Release notes | Confluence | Formatted, versioned |
Is this a quick, informal task?
├─ Yes → Trello
└─ No → Does it need sprint tracking or workflows?
├─ Yes → Jira
└─ No → Is it documentation?
├─ Yes → Confluence
└─ No → Consider tool complexity needs
When to escalate:
How to link:
Trello Card:
- Title: [ESCALATED] Original task name
- Description: Add "Escalated to Jira: PROJ-123"
- Archive card after Jira issue created
Jira Issue:
- Description: Include "Originally from Trello card [link]"
- Label: `from-trello`
Commands:
/trello get <card-id> - Get card details/jira-create - Create Jira issue with card content/trello comment <card-id> - Add Jira link to card/trello archive <card-id> - Archive original cardWhen to create docs:
Linking pattern:
Jira Issue:
- Add Confluence page link in comments
- Label: `documented`
Confluence Page:
- Include "Related issues: PROJ-123, PROJ-456"
- Use Jira macro to embed issue status
Commands:
/jira-get <issue-key> - Get issue details/confluence-create-page - Create doc with issue content/jira-comment <issue-key> - Add doc link to issueFull traceability pattern:
Git Commit: "feat: add user auth [PROJ-123]"
↓
Jira Issue: PROJ-123 (tracks implementation)
↓
Confluence: ADR for auth decision + API docs
↓
Release Notes: Generated from Jira fixVersion
Linking conventions:
feature/PROJ-123-user-authEnd-to-end release workflow:
1. PLANNING
└─ Jira: Create fixVersion, assign issues
2. DEVELOPMENT
└─ Code: Branch per issue, link commits
└─ Jira: Track progress in sprint
3. DOCUMENTATION
└─ Confluence: Update API docs, user guides
└─ Jira → Confluence: Create from issue details
4. RELEASE
└─ Jira: Mark fixVersion as released
└─ Confluence: Generate release notes from fixVersion
└─ Trello: Update roadmap board (if used)
Commands for release:
/jira-search fixVersion = "2.0.0" - Get all issues/trello update - Update roadmap card if applicable| Context | Format | Example |
|---|---|---|
| Commit message | [PROJ-123] | fix: login bug [PROJ-123] |
| Branch name | type/PROJ-123-desc | feature/PROJ-123-auth |
| PR description | Full URL or key | Fixes PROJ-123 |
| Confluence | Jira macro | {jira:PROJ-123} |
| Trello card | URL in description | Link to Jira issue |
Always link both directions:
1. Bug discovered
└─ Create: Jira bug issue (PROJ-123)
2. Investigation
└─ Jira: Add findings to description
└─ Confluence: Create post-mortem if major
3. Fix implemented
└─ Code: Branch `bugfix/PROJ-123-login-fix`
└─ Commit: `fix: resolve login issue [PROJ-123]`
4. Verified and closed
└─ Jira: Transition to Done
└─ Confluence: Update known issues if documented
1. Feature requested
└─ Jira: Create story/epic
2. Design phase
└─ Confluence: Create design doc
└─ Jira: Link design doc to epic
3. Implementation
└─ Jira: Break into sprint tasks
└─ Code: Link commits to tasks
4. Documentation
└─ Confluence: API docs, user guide
└─ Jira: Link documentation
5. Release
└─ Jira: Set fixVersion
└─ Confluence: Release notes
1. Start simple
└─ Trello: Create card for quick task
2. Scope grows
└─ Trello: Add checklist, realize complexity
3. Escalate
└─ Jira: Create formal issue
└─ Trello: Archive with link to Jira
4. Plan properly
└─ Jira: Add to sprint, estimate
└─ Confluence: Create requirements doc if needed
Use consistent naming across tools:
Consistent labeling helps cross-tool queries:
type:bug, type:feature, type:tech-debtpriority:high, priority:lowteam:frontend, team:backendCommon automation patterns:
When orchestrating cross-tool workflows, I will:
You: "I have a Trello card that's gotten complex. Should I move it to Jira?"
Me: "Let me check the card details.
[Uses /trello get <card-id>]
This card has:
Recommendation: Yes, escalate to Jira because:
I can:
Proceed?"
You: "We're releasing v2.0. What do I need to update?"
Me: "I'll coordinate the v2.0 release across tools.
Checklist:
Jira
/jira-search fixVersion = "2.0.0"]Confluence
Trello (if roadmap board exists)
Found 23 issues in v2.0.0. Ready to generate release notes?"