القائمة
agent-team: Complete an assigned task with evidence and artifact path.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | agent-team-task-complete |
| description | agent-team: Complete an assigned task with evidence and artifact path. |
| metadata | {"version":"1.0.0","openclaw":{"category":"agent-orchestration"},"requires":{"bins":["agent-team"],"skills":["agent-team-shared","agent-team-task"]},"cliHelp":"agent-team task complete --help"} |
PREREQUISITE: Read
../agent-team-shared/SKILL.mdand runagent-team sync checkfirst.
Mark an assigned task as done with concrete evidence and a run-scoped artifact path.
agent-team task complete --task TASK_ID --agent AGENT --evidence TEXT --artifact PATH [--force]
| Flag | JSON key | Required | Default | Description |
|---|---|---|---|---|
--task | task_id | yes | - | Task to mark done. |
--agent | agent | yes | - | Completing agent; must match the task assignee. |
--evidence | evidence | yes | - | Verification summary. Mention tests, inspected files, or decisions. |
--artifact | artifact | yes | - | Result file or directory path, normally under _workspace/{run_id}/. |
--force | force | no | false | Bypass sync conflict after explicit orchestrator approval. |
agent-team task complete --task task_docs --agent writer --evidence "Links verified." --artifact "_workspace/run_docs/task_docs.md"
agent-team task complete --task task_docs --agent writer --evidence "Accepted conflict." --artifact "_workspace/run_docs/task_docs.md" --force
agent-team task complete --params '{"task_id":"task_docs","agent":"writer","force":true}' --json '{"evidence":"Links verified.","artifact":"_workspace/run_docs/task_docs.md"}'
| Code | Meaning | Action |
|---|---|---|
agent_mismatch | Agent is not the task assignee. | Reassign or use the assigned agent. |
sync_conflict | Unread messages or incomplete dependencies. | Run sync check, resolve issues, then retry. |
validation_error | Required field is missing. | Provide task, agent, evidence, and artifact. |
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.
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.
Recipe: Stress-test a plan against repo code, docs, domain terms, and agent-team runtime constraints before execution. Use for 'grill the plan', 'challenge approach', 'refine planning', 'sharpen terminology', 'create acceptance criteria', or turning fuzzy ideas into durable tasks. Skip when plan is concrete with clear acceptance criteria and task contracts; go to architecture-design, coding, review, or compound-learning.