OpenParable
Skip to content
← Back to skills

Task Management

Productivity
task-management

Task Management is an Agent Skill for productivity published in the agentscope-ai/AgentTeams repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/agentscope-ai/AgentTeams/blob/HEAD/manager/agent/skills/task-management/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/task-management, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Task Management

Gotchas

  • Don't let Workers hallucinate on unfamiliar domains — when a task involves niche frameworks, complex APIs, or domain-specific workflows that the Worker likely lacks knowledge about, include a suggestion to use find-skills to search for relevant skills first. Skipping this leads to hallucinated code and wasted iterations
  • Delegation-first — always prefer assigning to a Worker over doing it yourself. Only self-execute when admin explicitly says "do it yourself" or the task is within your management skills
  • Never @mention a Worker after recording infinite task execution — this creates a rapid-fire loop (execute → report → trigger → execute → ...) that burns tokens continuously. Triggering happens only during heartbeat
  • Always use manage-state.sh to modify state.json — never edit manually with jq. The script handles atomicity, deduplication, and initialization
  • Every task assigned to a Worker MUST be registered in state.json — this includes coordination, research, review, and management tasks, not just coding tasks. If a task is missing from state.json, the Worker's container will be auto-stopped by idle timeout while still working
  • Always push task files to MinIO before notifying Worker — Worker needs to file-sync to get the spec
  • Always pull task directory from MinIO before reading results — Worker pushes results there
  • Read SOUL.md before composing notifications — use the persona and language defined there
  • Infinite task status is always "active", never "completed" — they repeat until explicitly cancelled

Operation Reference

Read the relevant doc before executing. Do not load all of them.

SituationRead
Admin gives task, no Worker specifiedreferences/worker-selection.md
Assign a one-off task or handle completionreferences/finite-tasks.md
Create or manage a recurring scheduled taskreferences/infinite-tasks.md
Need to update state.json or resolve notification channelreferences/state-management.md