Start Tasks
Use this skill to run execution continuously against an existing .tasks tree.
Primary Loop
- •Start by claiming work with
tasks grab. - •Implement the currently claimed work item(s).
- •When a task is complete, advance with
tasks cycle [TASK_ID](or justtasks cycleif context is set). - •Repeat indefinitely until the user stops the session or no work remains.
Batch Semantics
- •
tasks grabmay claim sibling batches by default. - •Complete each claimed task and call
tasks cycleas each task reaches done-state. - •Do not reset to
tasks grabbetween sibling completions unless context is lost.
CLI Efficiency (Avoid Repeated --help)
- •Do not call
tasks --helpor<command> --helproutinely. - •Use the command signatures below directly:
- •
tasks grab [--single|--multi|--no-siblings] [--agent AGENT] [--scope SCOPE] - •
tasks cycle [TASK_ID] [--agent AGENT] - •
tasks show [TASK_OR_SCOPE] - •
tasks blocked [TASK_ID] --reason "..." [--no-grab] - •
tasks skip [TASK_ID] [--no-grab] - •
tasks handoff [TASK_ID] --to AGENT [--notes "..."]
- •
- •Only consult help output if an invocation actually fails due to argument mismatch.
Operational Guardrails
- •Keep modifications bounded to the active claimed task context.
- •Run targeted tests before each
tasks cyclethat marks work complete. - •If blocked, use
tasks blocked --reason "..."promptly instead of stalling. - •Preserve dependency order; do not force-complete blocked tasks.
Reference
See references/tasks-cli-quick-reference.md.