Working on a Task
If no taskId is provided, call poll-task to get a new task.
Workflow
Get task details: Call
get-task-detailswith the taskId.Recall relevant memories: Use
memory-searchwith the task description before starting any work. Past learnings, solutions, and gotchas are indexed here.Choose your approach based on the task type:
- Research task → use
/researching - Development task → use
/planningfirst, then/implementing - Simple/direct task (no plan needed) → implement directly
- Research task → use
Work on it, calling
store-progressat each meaningful milestone (not just start and end — the lead monitors this).Complete the task — see Completion below.
Completion
Call store-progress with:
- Success:
status: "completed"+output: "<what you did and the result>". Output should be specific enough for the lead to assess without re-reading your work. - Failure:
status: "failed"+failureReason: "<what went wrong and what you tried>".
Then reply "DONE" to end the session.
Interruptions
If interrupted by the user, adapt to their instructions. When resuming, call /skill:work-on-task <taskId> again to pick up where you left off.
When to escalate
If you're stuck after genuine effort (not just first failure), use /skill:swarm-chat to ask the lead for help or clarification. Don't spin — escalate.