What problem does it solve? When you launch background feature agents via /kickoff, they run detached in tmux sessions or docker/podman containers, making it hard to know whether they are still working, stuck, waiting for input, or finished. This Skill gives you a consolidated status report without manually attaching to each session. ## Core Features & Use Cases - Multi-backend discovery: Finds agents both as docker/podman containers (via crosslink-agent labels) and as tmux sessions (feat-*), matched to this repo's git worktrees. - State classification: Reports each agent as Working, Idle, Waiting, Done, Error, or CI Failed by inspecting sentinel files (.kickoff-status), container state, and recent output. - Actionable next steps: Suggests follow-up commands such as viewing logs, attaching to tmux, reviewing committed changes, or relaying answers to waiting prompts. - Use Case: After kicking off three parallel feature agents, ask for a status check and get a compact table showing one agent still implementing, one done, and one waiting for your input on a CLI question. ## Quick Start Ask the assistant to check on the agents, for example by saying "check on the agents" or naming a specific session like feat-add-batch-retry.