TeamFlow
Client guides Sign in

TeamFlow in your editor

Every tool gets the same TeamFlow skills, the same stage vocabulary and the same command line. One line installs them where that tool looks: a skills directory, a rules file, an MCP server entry, whichever it reads. Each guide carries what the installer writes, the sign-in step, and the configuration to paste if you would rather do it by hand.

npx -y github:macleodlabs-ai/teamflow-plugin skills install --for cursor
Claude Code Automatic, via hooks /plugin install teamflow@macleodlabs Cursor Automatic, via hooks skills install --for cursor VS Code + Copilot Automatic, via hooks skills install --for copilot Windsurf Automatic, via hooks skills install --for windsurf Cline Automatic, via hooks skills install --for cline JetBrains AI Assistant Automatic, via hooks skills install --for jetbrains Zed Automatic, via git hooks skills install --for zed Claude Desktop Rules, then a git hook skills install --for claude-desktop OpenAI Codex CLI Automatic, via hooks skills install --for codex Gemini CLI Automatic, via hooks skills install --for gemini Aider Automatic, via git hooks skills install --for aider

Installing the skills is not the same as them being used: how much a tool reports on its own is on its card and in its guide. A team that needs the board to be complete also puts teamflow report in the git hook or the test script that already runs on every change.