Init
Scaffold a new agent-team project into the current directory (the engine and a starter roster — no sample project; you add your own). Use when the user wants to set up, initialize, scaffold, or create a new agent team project, or is starting from an installed plugin with no team yet.From its SKILL.md
npx -y skills add Kain1989/agent-team --skill initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
Scaffold an agent-team project into the current directory. Do it now.
- If
standup/team.jsonalready exists here, STOP and tell the user a team project is already present (don't overwrite) — point them at/agent-team:team-structure. - Otherwise copy the engine + starter files from the installed plugin into the current directory. The plugin root is
${CLAUDE_PLUGIN_ROOT}:
Then remove any copied runtime state:cp -R "${CLAUDE_PLUGIN_ROOT}/standup" ./standup cp "${CLAUDE_PLUGIN_ROOT}/setup.sh" ./setup.sh && chmod +x ./setup.sh cp "${CLAUDE_PLUGIN_ROOT}/.env.example" ./.env.examplerm -rf standup/.venv standup/control/jobs.db* standup/control/runs/* standup/control/worktrees/*(these are regenerated). If${CLAUDE_PLUGIN_ROOT}is unset (you're in a cloned repo, not an install), the files are likely already here — skip the copy. - Run
./setup.sh(venv, deps, gate config, runtime dirs). - Confirm and tell the user the next steps:
/agent-team:team-structureto see the roster,/agent-team:portalto open Mission Control,/agent-team:standupto run the team,/agent-team:add-team+/agent-team:add-roleto grow it, and/agent-team:add-projectto put the team on your own code —clone <git-url>,new <name>, oradopt <name>. The roster ships with no project squad, so/agent-team:standupwill stop until you add one.