القائمة
Send a task request to another Claude Code session by project name. Resolves short project names to full composite IDs automatically.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | st-send |
| description | Send a task request to another Claude Code session by project name. Resolves short project names to full composite IDs automatically. |
Send a TASK:REQUEST message to another active Claude Code session. The target can be a short project directory name (e.g., frontend) which gets resolved to the correct session automatically.
steop send <target> <description> [--mode=normal|flow] [--subject=SUBJECT] [--meta=JSON]
| Parameter | Required | Default | Description |
|---|---|---|---|
target | Yes | Project name suffix or full composite ID | |
description | Yes | Task description (all remaining positional args joined) | |
--mode | No | normal | Execution mode: normal (plain) or flow (full pipeline) |
--subject | No | auto | Message subject (defaults to first 80 chars of description) |
--meta | No | Additional JSON merged into the message meta |
target contains :, it is treated as a full composite ID (no resolution).project_dir:
/ (e.g., frontend matches /Users/dev/frontend).Send a simple task:
steop send frontend "Add a loading spinner to the dashboard page"
Send with flow mode for complex tasks:
steop send backend "Refactor the auth middleware to support JWT refresh tokens" --mode=flow
Send with a full composite ID:
steop send "hostname:/Users/dev/frontend:USER" "Fix the CSS regression in header"
Clarify phase of the workflow chain. Uses Opus to analyze the user's request, resolve ambiguities, define scope, and produce a clear task brief before research begins.
Execute phase of the workflow chain. Uses Haiku (simple), Sonnet (standard), or Opus (complex) to implement code changes according to a plan. Use when the user has an approved plan ready to execute.
Flow workflow chain that runs clarify → [research] → plan → execute → validate end-to-end without stopping. Pauses only on genuine ambiguity or circuit-breaker conditions.
Plan phase of the workflow chain. Uses Opus to design an implementation strategy. Use when the user wants to create a detailed plan before executing changes.
Research phase of the workflow chain. Uses Haiku (simple) or Sonnet (standard) to research the codebase and gather context for a task. Use when the user wants to investigate code before planning.
Validate phase of the workflow chain. Uses Sonnet to review and validate implementation changes. Use when the user wants to validate that code changes are correct and complete.