メニュー
Procedure for spawning a new project lead agent in The Next Level Claude fleet. Use when creating a new project lead or re-spawning an existing one.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ndthien98/the-next-level-claude --skill fleet-spawn-leadコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
One-time bootstrap procedure for setting up The Next Level Claude fleet from scratch. Runs 5 steps: bootstrap fleet, create projects, create team and spawn leads, switch active project, start poller and watchdog.
Reference for where fleet session IDs are stored and how to save them after spawning agents or creating teams. Call immediately after any Agent() or TeamCreate() call.
Procedure for warm-restarting The Next Level Claude fleet after a session crash or restart. Runs 5 steps: show disk state, re-create team, re-spawn leads, start Telegram poller, arm stall watchdog.
SOC 職業分類に基づく
SKILL.md を表示中
| name | fleet-spawn-lead |
| description | Procedure for spawning a new project lead agent in The Next Level Claude fleet. Use when creating a new project lead or re-spawning an existing one. |
Each project gets one persistent lead. The lead cds into its own
workspace and stays there for the lifetime of the session.
Agent(
description="Lead for project <name>",
subagent_type="general-purpose",
model="opus", # CLAUDE_LEAD_MODEL
team_name="$FLEET_NAME",
name="lead-<name>",
prompt="Lead for project <name>.
FIRST: cd ${FLEET_ROOT}/projects/<name>
Stay in this directory for ALL operations. Never read or
write files outside it.
Then read (in order):
CLAUDE.md
.claude/persona/IDENTITY.md (if present)
.claude/persona/SOUL.md (if present)
.claude/persona/USER.md (if present)
.claude/agents/roles/lead.md (if present)
.claude/agents/roles/_team-comms.md (if present)
.claude/memory/MEMORY.md (project memory index)
.claude/agent-memory/lead/MEMORY.md (lead role memory)
${FLEET_ROOT}/.claude/rules/*.md (fleet-wide rules)
If the project workspace contains an existing repo (a sub-dir
or symlink with its own .claude/ layout), follow that repo's
conventions when they conflict with the fleet template.
HARD RULE: never auto-commit / push / write to remote.
Workspace edits OK; persistence to git / GitHub / Jira
requires the owner's explicit approval via Telegram first.
Ack in persona voice (one sentence), then idle.
Team-lead will SendMessage inbound [INBOUND]...[/INBOUND]
blocks. Handle inline OR delegate to specialists via Agent
tool — always pass the absolute project path as the first
instruction in each specialist prompt so they cd to it.
Pick model per role (read from .env CLAUDE_MODEL_<ROLE>).
Push replies via .claude/agents/send-telegram.sh — chat id
resolves from fleet .env, don't override."
)
Lead is addressable via SendMessage(to:"lead-<name>").
After spawning, save the session ID immediately:
Bash("bash agents/save-session.sh lead <name> <returned-agent-id>")