dist/claude/plugins/dev-flow/skills/watch-team/SKILL.md
Monitor a Claude Code team in tmux, auto-approve prompts, and report status. Use when the user says "watch the team", "monitor agents", "auto-approve", "babysit team", or "agents are stuck". NOT for single-agent monitoring, non-tmux setups, or general process supervision.
npx skillsauth add alexei-led/claude-code-config watch-teamInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Monitor all panes in a tmux window running a Claude Code team. Detect stuck agents waiting on approval prompts, auto-approve them, and report task/team status.
~/.claude/tasks/<team>/ for in_progress and
pending tasks.WINDOW="ccbot:3"
PANE="1"
DURATION="${2:-300}"
END=$((SECONDS + DURATION))
while [ $SECONDS -lt $END ]; do
output=$(tmux capture-pane -t $WINDOW.$PANE -p 2>/dev/null)
if echo "$output" | grep -q "Do you want to proceed?"; then
tmux send-keys -t $WINDOW.$PANE Enter
echo "$(date +%H:%M:%S) Approved prompt in pane $PANE"
fi
sleep 3
done
If the lead pane is at 100% budget or under 5% context:
tmux list-panes -t <window> -F '#{pane_index} #{pane_pid}' | while read idx pid; do
kill $pid 2>/dev/null
done
Then commit remaining work manually with git.
tmux ls; ask the user which window to watch.~/.claude/tasks/<team>/ missing: skip task-status check and note it in the report.## Team Status — <window>
Watched: <duration>s | Panes: <N>
### Unblocked
- pane <N>: approved prompt at <HH:MM:SS>
### Task States
- <task>: in_progress / pending / done
### Warnings
- lead pane at <X>% context budget
tools
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
development
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
tools
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
tools
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.