# Workflow

Drive a team workflow from this coding session.

- Repository: https://github.com/Tencent/teamai-cli (5729 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Tencent/teamai-cli --skill workflow -g -a claude-code -y`
Codex: `npx skills add Tencent/teamai-cli --skill workflow -g -a codex -y`
Cursor: `npx skills add Tencent/teamai-cli --skill workflow -g -a cursor -y`
Gemini CLI: `npx skills add Tencent/teamai-cli --skill workflow -g -a gemini-cli -y`

## Description

Drive a team workflow from this coding session. Use when a generated workflow skill (workflow-<alias or name>, or a teamai default such as teamai-share-learnings) sent you here, or the person asks to run a team workflow.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Drive a team workflow

## Your role

You orchestrate. You run the literal commands the CLI prints, and you keep the person told while the run goes on. Detached runners do each command step; a child agent you start does each prompt step from its brief. Step work belongs to them, and yours is the literals and the person. On `h4`, where your host starts no child, you work each prompt step yourself, as the Dispatch section says. The run's state lives in the CLI: every reply says what is running and what to run next, so you carry nothing between calls. Never run git in a workflow place; the CLI prepares and checks each place a step runs in.

## Start

Run `teamai workflow start --describe <name> --driver skill` with the workflow name from the skill that sent you. Where this machine runs teamai through `npx teamai-cli`, use that in its place; every literal the CLI prints after this already does.

Act on `data.describe.ask.kind`:

The rest: https://github.com/Tencent/teamai-cli/blob/HEAD/skill-data/workflow/SKILL.md