TeamFlow in Kiro

1. Install

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

That writes:

• .kiro/skills/<skill>/SKILL.md — the twelve skills, in the skills directory Kiro reads
• .kiro/steering/teamflow.md — the reporting instruction, as a Kiro steering file
• .kiro/settings/mcp.json — the TeamFlow MCP server under mcpServers
• .teamflow/hooks/kiro.sh — the hook itself; it calls teamflow hook --for kiro, prints nothing the tool could read as a denial, and exits 0 whatever happens
• .kiro/hooks/teamflow.json — the hook registration: SessionStart, UserPromptSubmit, PostToolUse, Stop and SessionEnd

Add --scope user to install for every project on this machine, or --dry-run to see the file list without writing anything. Re-running it replaces TeamFlow's block and leaves the rest of each file alone.

Then sign this machine in, and check it. The hooks above report nothing at all until there is a credential, and nothing errors while they do not: an install that is never signed in looks exactly like a working one until somebody notices the board is empty.

npx -y github:macleodlabs-ai/teamflow-plugin login
npx -y github:macleodlabs-ai/teamflow-plugin status

login opens a browser once and stores a revocable refresh token; login --device prints a code to type into a browser on another machine instead. status answers with the organisation, the project and the repository this checkout reports to, and identity: not signed in there is the one thing to fix before expecting anything on the board.

2. What TeamFlow can do in Kiro

This list comes from Kiro's own documentation, checked 2026-10-04. We have not run Kiro with TeamFlow yet.

• Yes: Ticket, project and lead notes at session start.
• Yes: Ticket, project and threads with each prompt.
• Yes: Plan goes on when a turn ends.
• Yes: TeamFlow skills.
• Yes: TeamFlow MCP server.
• Partly: Helper agents and session end on the board. Kiro has no events for helper agents. Only Kiro CLI reports session end.
• No: Allow or Deny from TeamFlow. Kiro has no event for a permission. Holding every tool call would stop Kiro.
• No: One-minute check-in on an idle session. Kiro cannot wake an idle session later.

To add these to an earlier install, run npx -y github:macleodlabs-ai/teamflow-plugin hooks install --for kiro again. Every tool side by side.

3. The skills you get

The same twelve the Claude Code plugin carries, generated from the same SKILL.md files. This tool loads them as skills, one directory each, with the name prefixed so they do not collide with anybody else’s in a shared directory.

Each one wraps a github:macleodlabs-ai/teamflow-plugin subcommand, so the skill and the shell command are the same thing. Inside Claude Code they are /teamflow:login, /teamflow:status and so on.

4. Sign in once

Kiro opens the sign-in page the first time it uses the server. The hooks need this machine signed in too:

npx -y github:macleodlabs-ai/teamflow-plugin login

5. By hand

The installer writes this for you. If you would rather paste it: .kiro/settings/mcp.json.

{
  "mcpServers": {
    "teamflow": {
      "url": "https://codercat.io/mcp"
    }
  }
}

When a session starts and when you send a prompt, Kiro gets your ticket and project in its context. When Kiro stops and the plan has a next step, TeamFlow tells Kiro to go on. Kiro has no event for a permission or a question, so you answer those in Kiro, not in TeamFlow.

6. Uninstall

npx -y github:macleodlabs-ai/teamflow-plugin skills uninstall --for kiro

That removes exactly what the install above wrote: its own files go, and its own entries come out of the files it shares with your editor's other hooks and servers, which are left as they were. A hook TeamFlow did not write is never touched, and uninstalling something that is not there succeeds quietly. --dry-run prints the list without removing anything.

npx -y github:macleodlabs-ai/teamflow-plugin hooks uninstall --all is the bigger hammer: every tool at once, the git hooks, and this repository's ticket binding.

7. The stages to report

BACKLOG is the thirteenth: the ticket exists and nothing has started. Statuses are running, success, waiting, blocked, failed and idle. This is the same vocabulary the Claude Code plugin derives, so a ticket moved from here sits in the same column as one moved by Claude.

8. Without the agent

Anything that runs in a shell posts the same report with no model involved. A git hook, an npm script, a run configuration, a CI step:

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. Prefer it wherever the board has to be right whether or not an agent remembered. npx -y github:macleodlabs-ai/teamflow-plugin report --help lists every flag.

9. What this is not

Kiro reports automatically through its own hooks: SessionStart, UserPromptSubmit, PostToolUse, Stop and SessionEnd. Nothing to remember. Kiro hooks report every tool call, prompt and turn end, in the IDE and in Kiro CLI. TeamFlow adds your ticket to the chat and tells Kiro the next plan step. Checked against the vendor’s own hook documentation on 2026-10-04: kiro.dev/docs/hooks/types documents stdin JSON with hook_event_name, cwd, session_id, plus prompt, tool_name, tool_input, tool_response and assistant_response. Hook actions: "Exit code 0: Hook succeeded. STDOUT is added to context (SessionStart, UserPromptSubmit) or ignored (others)." A Stop hook may return {"decision": "block", "reason": ...}, and "the reason is sent as a new user message to the agent". No permission or question event exists, and SessionStart and SessionEnd are "V3" only on the CLI.

The hooks see this tool's own calls and nothing else. A test run in another terminal, a merge from the web UI, a deploy from a pipeline: put npx -y github:macleodlabs-ai/teamflow-plugin report in the git hook or the script that already runs on every change, and those land on the board too.

10. What leaves your machine

TeamFlow manages your AI software factory. It is run by MacleodLabs. Your code stays inside your organisation: the local plugin sends derived state only, a ticket key, a stage, a status, a short summary and evidence links. Prompts, diffs, source code, commands and logs are never sent and are rejected before they are charged.

• Every client
• llms.txt
• Capabilities
• The reporting contract, in full