メニュー
Add a teammate — one command (`aw team add … --start`) materializes an instance's home from a blueprint profile, sets up its isolated git worktree, and launches it. Use when a human asks for a teammate or assigned work needs one.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | spawn-instance |
| description | Add a teammate — one command (`aw team add … --start`) materializes an instance's home from a blueprint profile, sets up its isolated git worktree, and launches it. Use when a human asks for a teammate or assigned work needs one. |
An instance is a runnable teammate with its own aweb identity, a home, and —
for code roles — an isolated git worktree. Since aw 1.31, aw team add … --start
does the whole thing in one command: it materializes the home from a blueprint
profile, sets up the worktree isolation, and launches the runtime — no manual
invite / accept / init / symlink / git worktree add dance.
Spawn when a human asks, or when assigned work needs a teammate — not on your own initiative to "get help".
aw reads your identity from the current directory's .aw, so run this from
your own home (it uses your team's authority to add the member):
aw team add <name>@aweb.team/<role>=<runtime> --start \
--home <abs/path/to/agents/instances/<name>> \
--session <tmux-session> --no-attach
<role> is a profile in the blueprint (developer, reviewer,
proofreader, …); <runtime> is claude-code or pi. Override the
blueprint with --blueprint / AWEB_BLUEPRINT (default aweb.team).--start materializes the home from the public blueprint (an
auth-less read), sets up <home>/worktree/ — a git worktree on the
agent's own branch — plus a work-main/ symlink for coordination roles
(works_on_main), then launches the runtime in tmux with channel preflight,
trust/dev-channel prompt auto-answering, and pi --approve. It connects to
the channel on its own.--session <name> + --no-attach — put the window in a named tmux
session and don't attach. Use a fresh/throwaway session so you never touch
a live team's session. --recreate is refused when the target session holds
running agent windows; --force-kill is the explicit override that kills
them. Prefer a fresh --session over ever reaching for --force-kill.--home overrides the default agents/instances/<name>. Never move or
rename a home after materialization — aweb registers the identity at its path.The agent runs aw from its home and does all git/builds from worktree/.
Verify: aw workspace status shows the new member active; the tmux pane shows
the runtime up (claude: bypass permissions on; pi: ✓ aweb connected).
Drop --start to just materialize + isolate the home; launch it later with
aw team up (same launch path). Use this when you want the home staged before
running it.
When the teammate is no longer needed, use the retire-instance skill (revoke
the membership, remove the worktree + home).
Check and set up the aweb channel connection. Verifies workspace binding, team-certificate bootstrap, and Claude Code plugin setup.
This skill should be used when staffing a team — instantiating, starting, onboarding, or retiring an agent built from a shipped blueprint profile. Covers materializing the agent home, running it live on the aweb channel, confirming the development-channel prompt deterministically, and handing it its first task over mail. The mechanics that turn a profile into a working teammate.
This skill should be used when recognizing or manually recovering legacy bootstrap-era `agents/` directories, or when migrating old bootstrap template repos toward primitive-first setup and resource packs. The `aw agents` command family is retired; do not recommend running it.
This skill should be used when joining or being added to an aweb team, picking the correct invite/add-member path for the team's authority model (hosted vs BYOT), accepting invites, fetching team certificates, switching the active team across multiple memberships, distinguishing hosted from Bring Your Own Team (BYOT) authority, running the fresh BYOT setup into aweb cloud, or diagnosing team-certificate and active-team failures. Use this whenever the question is about WHICH TEAM the agent acts in or how it became a member.
Remove a teammate — delete an instance's aweb identity and workspace, then its home, worktree, and branch. Use when an instance's job is done (a developer whose branch merged, a reviewer that gave its verdict).
How any agent grows its soul as it works — adding to its docs, decisions, memory, and skills (but never its AGENTS.md or role). Use whenever you learn something durable mid-work that a future instance of you should keep.