trello-cli

trello-cli-claude

A Claude Code plugin for natural language Trello integration. Manage your Trello cards, track bugs, and organize tasks directly from your Claude Code sessions.

Overview

This plugin wraps trello-cli, providing Claude Code with skills to:

• Work on cards - Fetch card details, download attachments, and start work
• File bugs - Capture session context into new Trello cards
• Finish cards - Move completed cards to the appropriate Done list

Prerequisites

1. trello-cli must be installed and configured in your project:
   • Add trello-cli to your Gemfile
   • Run bundle install && bundle binstubs trello-cli
   • Create .trello.yml with your board ID and default list
   • Set TRELLO_API_KEY and TRELLO_TOKEN environment variables

See the trello-cli documentation for setup details.

Installation

Via Plugin Marketplace

/plugin marketplace add mjbellantoni/trello-cli-claude
/plugin install trello-cli-claude

Local Development

claude --plugin-dir /path/to/trello-cli-claude

Skills

/work-on-card

Start working on a Trello card. Recognizes natural language references:

• "fix #123"
• "work on card abc123"
• "tackle that bug"

What it does:

1. Fetches card details (title, description, labels, checklists)
2. Downloads all attachments (screenshots, stack traces)
3. Moves card to "In Progress"
4. Routes to appropriate workflow based on labels (bug → debugging, other → brainstorming)

/file-bug

Capture an issue you encountered into a new Trello card:

• "file a bug for that"
• "create a ticket"
• "that's a bug - capture it"

What it does:

1. Gathers context from the session (error, steps, expected/actual behavior)
2. Formats a structured bug report
3. Creates card with bug label at top of Inbox
4. Attaches stack traces or screenshots if available

/finish-card

Complete a card and move it to the appropriate Done list:

What it does:

1. Checks for recent commits to determine destination
2. Moves to "Done/Committed" (if code was merged) or "Done/Deployed" (if no code changes)
3. Asks for clarification if ambiguous

/create-parent-from-plan

Set up a parent card with a numbered checklist of steps:

• "create a parent card for this plan"
• "make a parent Trello card with checklist"

What it does:

1. Creates a card with [slug] title format on Backlog
2. Adds plan/context as the description
3. Creates a "Steps" checklist with numbered items (01, 02, ...)

/start-next-child

Start work on the next ready checklist item:

• "start next checklist item"
• "grab the next item and make a child card"

What it does:

1. Parses the parent's checklist for deps, migration tags, and completion status
2. Finds the first ready item (unchecked, deps satisfied, migration lock clear)
3. Creates a child card [slug.NN] step title on In Progress
4. Links the child back to the parent checklist item
5. Reports blocked items if nothing is ready

/file-findings

Batch-file code review findings as individual Trello cards:

• "file findings 02 03 04"
• "create cards for findings"

What it does:

1. Looks up each finding identifier in the current session's review output
2. Classifies as bug (broken behavior now) or chore (everything else)
3. Creates a self-contained card with file paths, code context, and fix direction
4. Places each card at top of Inbox with the appropriate label
5. Reports a summary table of card titles and URLs

Each card description is fully self-contained — a new Claude instance with no session history can complete the work from the description alone.

/complete-child

Complete a child card and update the parent:

• "mark this child done"
• "complete this and check off parent"

What it does:

1. Moves child to Done/Committed or Done/Deployed (same logic as finish-card)
2. Checks off the corresponding parent checklist item

Parent/Child Workflow

Conventions

Convention	Format	Example
Parent title	[slug] description	[owner-data] Owner data ingestion
Child title	[slug.NN] step title	[owner-data.01] Create schema
Checklist numbering	Two-digit, zero-padded	01. 02. ... 10. 11.
Dependencies	{deps:NN,NN}	{deps:01,02}
Migration tag	{migrations}	{migrations}

Example Checklist

Steps: (1/4)
  [x] 01. Create owner schema {migrations}
  [ ] 02. Add API endpoints {deps:01}
  [ ] 03. Backfill job {deps:01,02}
  [ ] 04. Add ingestion worker {deps:03} {migrations}