symphony-trello: Skill for Codex

Debug

Goals

• Determine whether the problem is Trello routing, scheduler state, Codex execution, filesystem access, credentials, or handoff tooling.
• Use safe identifiers and avoid exposing secrets or private local paths.
• Leave enough evidence for the next agent to continue.

Inputs

• Trello card title or short link.
• The workflow file for the board.
• The status page or /api/v1/state.
• Service logs from the local run or deployment.
• Recent Trello comments on the card.

Triage Flow

1. Confirm the service is reading the intended workflow file and Trello board.
2. Run symphony-trello diagnostics when the installed command is available. This gives a public-safe overview of connected boards, workflows, health probes, and recent logs.
3. If the failure depends on information the default report intentionally omits, run symphony-trello diagnostics --deep to add deeper public-safe checks such as Codex and GitHub auth-status probes.
4. If the diagnostics output contains board_hash, key_hash, or <path:...> tokens that you need to map back to local objects, run symphony-trello diagnostics --show-private-context locally. Add --board or --workflow when you can narrow the scope. Treat this output as private investigation data: use it to inspect the right board, workflow, env file, workspace, state directory, or log file, but do not paste it into GitHub, Trello, committed files, or user-facing summaries.
5. Open /api/v1/state and check:
   • queued candidates
   • running cards
   • retrying cards
   • last Codex event and message
   • token totals and rate-limit data
6. Check the card's current Trello list. Cards in non-active lists are not dispatched.
7. Read recent Trello comments on the card. Blocker comments often describe the requested path, the per-card workspace, auth, or permission problem without copying private host paths into Trello-visible text.
8. Search logs by card identifier, worker identity, and session id. Prefer rg.
9. Classify the failure:
   • Trello credentials or board access.
   • Workflow parse or invalid config.
   • No eligible active cards.
   • Codex app-server startup/auth failure.
   • Codex turn timeout or stall.
   • Filesystem sandbox or allowed-root blocker.
   • Trello handoff tool failure.
10. Fix the smallest cause, then rerun a local or deployed live verification that exercises the same path.