Demo — accounts will be reset at launch, and the server is restarted regularly during this week's build phase.
TeamFlow
Docs Client guides Sign in

All documentation

Other tools

The board does not care which tool moved a ticket. It cares that something reported it. Every tool gets the same skills, the same stage vocabulary and the same command line; only the install path differs.

One command per tool

npx -y github:macleodlabs-ai/teamflow-plugin skills install --for cursor

--for takes cursor, codex, gemini, copilot, windsurf, cline, zed, jetbrains, claude-desktop, aider and claude-code. Add --dry-run to list the files without touching any of them.

That writes the skills where your tool discovers them, or generates the rules file it reads instead, registers TeamFlow's MCP server in that tool's own format, and installs its hook configuration where it has one. Re-running replaces TeamFlow's block and leaves the rest of each file alone.

Then sign in once, exactly as in get started.

How much is automatic

  • Through their own hooks: Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf, Cline, OpenAI Codex CLI, Gemini CLI and JetBrains AI Assistant. Nobody types a command and nobody instructs the model.
  • Through git hooks: Zed and Aider have no agent hooks, so commits, merges and pushes report by themselves.
  • Through its rules file: Claude Desktop has no hooks at all and reports because its rules tell it to. A git hook keeps the board complete when it forgets.

Installing the skills is not the same as them being used. Where the level is rules, reporting is still the model's decision — which usually happens and sometimes does not. A team that wants the board complete without depending on that puts a report into the places that already run on every change.

Reporting from anything with a shell

npx -y github:macleodlabs-ai/teamflow-plugin report --issue DAEMON-142 \
  --stage LOCAL_TEST --status success --summary "42 tests, 0 failing"

Same envelope, same transport, same credential, no model involved. It is the answer for a pre-push hook, an npm script, a CI step that is not GitHub Actions, or a JetBrains run configuration.

It never decides whether your push happens. It exits successfully on a refused, queued or unreachable service, so a TeamFlow outage cannot block a developer.

A guide for each tool

Every tool has its own page, with what the installer writes, where it writes it, and the configuration to paste if you would rather do it by hand.

Next