manage-tasks
Streamline spec implementation workflow by managing tasks: mark in-progress, implement, and complete. Use actions like set-status, list, get, and next-pending to track progress effectively.
Instructions
Task management for spec implementation. REQUIRED SEQUENCE: First mark task as in-progress, then implement, finally mark as completed. ALWAYS update status to in-progress before starting work. Implementation workflow: set-status (in-progress) → code → set-status (completed). Status markers: [] = pending, [-] = in-progress, [x] = completed
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | Action: list all tasks, get specific task, set task status, get next pending task, or get full implementation context | list |
| projectPath | Yes | Absolute path to the project root | |
| specName | Yes | Name of the specification | |
| status | No | New task status (required for set-status action) | |
| taskId | No | Specific task ID (required for get, set-status, and context actions) |
Input Schema (JSON Schema)
{
"properties": {
"action": {
"default": "list",
"description": "Action: list all tasks, get specific task, set task status, get next pending task, or get full implementation context",
"enum": [
"list",
"get",
"set-status",
"next-pending",
"context"
],
"type": "string"
},
"projectPath": {
"description": "Absolute path to the project root",
"type": "string"
},
"specName": {
"description": "Name of the specification",
"type": "string"
},
"status": {
"description": "New task status (required for set-status action)",
"enum": [
"pending",
"in-progress",
"completed"
],
"type": "string"
},
"taskId": {
"description": "Specific task ID (required for get, set-status, and context actions)",
"type": "string"
}
},
"required": [
"projectPath",
"specName"
],
"type": "object"
}