Wholesale AI Champions Claude Code playbook
← Champions

Lei Hua

Firefly · .NET · ADESA Workflow · QA harness

I’m on the Firefly team, so my day-to-day flow lines up with Rich’s writeup — same plugin, same harness, same set of trade-offs. The angle below is what’s actually clicked for me as a daily user, plus the MCP set I keep connected.

ADESA Workflow + the harness, every day

The two pieces I run on are:

  • ADESA Workflow plugin for the plan → implement → PR loop. I work out of the centralized planning repo and let the /aw-* commands carry stories into the code repos so I’m not re-stating context every time I context-switch between services.
  • firefly-harness for the validate side of RPIV. The inbox tells me what PRs and stories actually need me right now; the session view keeps the QA pass — checklist, Claude Code chat, evidence — in one place instead of scattered across PR comments, ADO, and Slack.

Both surfaces are still moving and we treat that as the point. When /aw-pr or /aw-verify shifts, or the harness adds a new pane, the right move is usually to try it on the next ticket rather than wait for the dust to settle.

MCPs

The set I keep connected, in rough usage order:

  • Azure DevOps — work-item context, queries, linking PRs back to PBIs.
  • Context7 — current library docs so Claude isn’t reasoning from a stale snapshot.
  • repo-reader — read across multiple local repos without cd-ing around or losing the working directory.
  • Slack — pulling channel and DM context into the terminal instead of switching tabs.
  • Google Drive — Docs, Sheets, and Calendar.
  • Snowflake — wholesale analytics queries directly from Claude.

Most of these have install commands on the MCPs page. repo-reader is the one that isn’t there yet but is worth adding.

Tip: let Claude audit your tooling

If you’re not sure whether your MCP / CLI / plugin set is actually right for the repo you’re sitting in, run /essentials:essentials-setup-tools. It does a repo-aware audit of installed MCP servers, CLI tools, and marketplace plugins, then recommends what to add or remove based on what the codebase actually uses. Faster than reading through the MCP page and guessing.