| name | tasks-execute |
| description | Use this skill when: the user runs /tasks-execute, asks to execute backlog tasks, or wants the next queued task delivered from .agents/tasks. Trigger keywords: tasks-execute, execute task, backlog execution, next task. |
| argument-hint | Optionally describe execution constraints or priority guidance |
Tasks Execute Skill
This skill executes backlog tasks one at a time inside the .agents/tasks/
workspace.
When to Use
- The user runs
/tasks-execute.
- The user asks to execute the next backlog task.
- The user wants task delivery managed linearly through backlog, in-progress, and done.
Workflow
- Select the highest priority task in
.agents/tasks/tasks/backlog/.
- Confirm
.agents/tasks/tasks/in-progress/ is empty before starting work.
- Move the selected task file into
.agents/tasks/tasks/in-progress/.
- Implement the feature or fix end-to-end based on the task description and relevant codebase files.
- Verify the result with the appropriate checks for the change.
- Move the task file from
in-progress/ to .agents/tasks/tasks/done/.
- Update
.agents/tasks/PROGRESS.md with the delivered outcome and business impact.
Execution Rules
- Only one task may be in progress at a time.
- Do not skip verification before marking a task done.
- Keep implementation scoped to the selected task unless a dependency forces a minimal adjacent change.
