Menu
agent-team: Create an assigned task inside a run.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Design, create, evolve, or audit Codex-native harnesses for Agent Team projects. Builds specialized .codex/agents, .agents/skills, an orchestrator skill, AGENTS.md pointers, validation, and an evolution loop. Use for 'set up codex harness', 'create codex automation', 'build specialist agents', harness updates, harness audits, sync, status, and follow-up refinement. Generated harnesses default orchestrated runtime execution to Agent Team runtime skills backed by daemonless `agent-team` state.
agent-team: Complete an assigned task with evidence and artifact path.
Designer persona for agent-team design work. Routes between deep design interview (brief) and artifact production (spec). Use for 'design this', 'design discovery', 'design interview', 'produce design spec', 'visual/UI/icon/character/environment/logo/design-system design'. Skip for backend architecture (use persona-agent-team-planner), implementation code, code review, run execution, worker checkpoints, audits, or learning capture.
Planner persona for agent-team pre-execution work. Routes between terminology alignment, plan stress-testing, and backend architecture design before coding starts. Use for 'plan this', 'align terms', 'grill the plan', 'propose backend structure', or any pre-implementation discovery for code/architecture. For visual/UI/icon/character/environment/logo/design-system work use persona-agent-team-designer instead. Do not use for run execution, worker checkpoints, audits, learning capture, or direct coding.
Deep design interview that produces a design brief. Socratic 4-line probes lock the design's output description, tensions, assumptions, priorities, and failure modes. Output: design-brief.md. Skip for backend architecture, terminology cleanup, fuzzy planning, implementation, review, post-run learning, or rendered assets. Hand off to recipe-agent-team-design-spec for artifact production.
Generic spec producer for locked design briefs. Consumes design-brief.md, reads the Output description, consults pattern hints from references/, and produces artifacts under the brief's Output Path. Skip when no brief exists; run recipe-agent-team-design-interview first. Skip for backend architecture, code, review, or post-run learning.
| name | agent-team-task-create |
| description | agent-team: Create an assigned task inside a run. |
| metadata | {"version":"1.0.0","openclaw":{"category":"agent-orchestration"},"requires":{"bins":["agent-team"],"skills":["agent-team-shared","agent-team-task"]},"cliHelp":"agent-team task create --help"} |
PREREQUISITE: Read
../agent-team-shared/SKILL.md.
Create a task assigned to one agent, optionally with dependencies.
agent-team task create --run RUN_ID --agent AGENT --title TITLE [--id TASK_ID] [--depends-on TASK_ID] [--body TEXT] [--metadata JSON_OBJECT]
| Flag | JSON key | Required | Default | Description |
|---|---|---|---|---|
--run | run_id | yes | - | Owning workflow run. |
--agent | agent | yes | - | Assignee expected to start, block, or complete the task. |
--title | title | yes | - | Compact task label. Put detailed instructions in --body. |
--id | id | no | generated | Stable task ID. |
--depends-on | depends_on | no | [] | Task ID that must be done; repeat flag or use a JSON array. |
--body | body | no | empty | Worker contract: scope, expected output, and constraints. |
--metadata | metadata | no | {} | JSON object for structured context. |
agent-team task create --run run_docs --agent writer --title "draft API docs" --body "Use the research artifact."
agent-team task create --params '{"run_id":"run_docs","agent":"writer","title":"draft API docs","depends_on":["task_research"]}' --json '{"body":"Use the research artifact.","metadata":{"scope":"api"}}'
| Code | Meaning | Action |
|---|---|---|
validation_error | run_id, agent, or title is missing. | Provide required fields. |
invalid_json | metadata is not a JSON object. | Use an object such as {"scope":"api"}. |