Sprint Board That Updates Itself — Trello Cards Move With the Code

The Problem

Project management boards are beautiful lies.

You set them up with optimism. Color-coded labels. Swim lanes. Due dates. Then reality hits. Developers push code but forget to move the card. Cards sit in "In Progress" for three weeks because nobody updates them. The PM spends 20 minutes in standup asking "is this still in progress?" and getting blank stares.

I ran a Trello board for PyratzLabs. Three weeks in, the board reflected reality with about 40% accuracy. Cards in "Done" that were actually blocked. Cards in "To Do" that were already merged. One card still assigned to someone who'd left the project.

The board became decoration. We stopped looking at it. We went back to Slack threads and memory — which is exactly the chaos a board is supposed to prevent.

The problem isn't discipline. The problem is that updating a board is a separate action from doing the work. Separate actions get forgotten. Always.

The Solution

The agent watches CI/CD events and git activity, then moves Trello cards automatically. Code pushed? Card moves. Pipeline passes? Card moves. Merge complete? Card moves to Done with the merge link attached. Blocked? Red label, comment with the reason.

The board becomes a live mirror of actual project state. No human updates required.

The Process

The integration chains GitLab webhooks through the agent to the Trello API:

# Webhook listener config
webhooks:
  gitlab_pipeline:
    event: pipeline_success
    action: |
      trello move-card \
        --card "$(git log -1 --format=%s | grep -oP 'TRELLO-\d+')" \
        --list "Review" \
        --attach "$(CI_PIPELINE_URL)"

  gitlab_merge:
    event: merge_request_merged
    action: |
      trello move-card \
        --card "$TRELLO_CARD_ID" \
        --list "Done" \
        --comment "Merged: $CI_MERGE_REQUEST_URL"
        --remove-label "In Progress" \
        --add-label "Shipped"

When a blocker is detected — failed dependency, missing API key, stuck pipeline — the agent acts:

# Agent detects blocker and updates Trello
trello update-card \
  --card "TRELLO-142" \
  --add-label "Blocked" \
  --comment "🚫 Blocked: auth service dependency not deployed.
  Waiting on TRELLO-138 (API key provisioning).
  Estimated unblock: pending DevOps review."

Every Friday, the agent sends a board snapshot to Telegram:

📊 Weekly Sprint Summary — Week 11

✅ Done: 8 cards
🔄 In Progress: 3 cards
🚫 Blocked: 2 cards
  - TRELLO-142: Auth dependency (3 days)
  - TRELLO-155: API key missing (1 day)

⏱ Avg cycle time: 2.4 days
📈 Velocity: 8 points (up from 6 last week)

No standup required to know the state. The board is the truth, and the truth updates itself.

The Results

The blocker detection time is the biggest win. A card that's blocked for 12 hours before anyone notices is 12 hours of compounding delay. Catching it in 5 minutes means someone can unblock it the same day.

Try It Yourself

1. Set up GitLab/GitHub webhooks pointing to your Mr.Chief agent
2. Map commit messages or branch names to Trello card IDs (e.g., TRELLO-142)
3. Define state transitions: pipeline pass → Review, merge → Done, failure → Blocked
4. Configure weekly Telegram digest with board snapshot

Convention matters: if developers include the card ID in their commit messages, the automation is seamless. If they don't, you need branch-name mapping. Pick one and enforce it.

A project board that requires manual updates is a project board that lies. Automate the truth.