From cotask
Marks tasks ongoing in TASKS.md and begins execution. Triggers on 'start', 'work on', task slugs like #fix-auth, or /starting-task.
npx claudepluginhub wbopan/cotask-marketplace --plugin cotaskThis skill uses the workspace's default tool permissions.
- Args: {{ARGS}}
Looks up tasks by ID or name, marks them in-progress, starts worklogs if enabled, executes using tools like EnterPlanMode and Bash, then completes via /complete-task. Use to pick up and execute tasks.
Looks up task by ID or name with taskmd, reads details, marks in-progress, starts worklog if enabled, executes using tools like EnterPlanMode, and completes it. Use to pick up and run predefined tasks.
Defines conventions for TASKS.md files: structure with optional sections, status symbols ([ ] todo, [/] ongoing, [x] done, [-] backlog), task descriptions, and testable acceptance criteria. Use for creating, editing, updating tasks or tracking progress.
Share bugs, ideas, or general feedback.
!cat TASKS.md 2>/dev/null || echo "No TASKS.md found in current directory"
This is the "start button" for task execution. It ensures the task is tracked in TASKS.md before any work begins, so the dashboard stays in sync.
Look at what the user gave you in the args:
#slug (e.g. #fix-auth-bug): Match it against TASKS.md. If there's no match, say so and stop — don't guess./creating-task skill to create the task first, then continue from step 2./creating-task to create it first.Important: Never skip task creation. If no task exists in TASKS.md for what the user wants to do, create it first via /creating-task. Do not jump to solving the problem without a tracked task.
[/]Edit TASKS.md to change the task's status to [/]. Do this before any other output.
If the task status is:
[ ] → Edit it to [/].[/] → Already ongoing. Skip the edit.[x] or [-] → Tell the user and ask if they want to reopen it.Read the task's description and AC. Before touching any code:
Respect the user's args and the task description. If either one contains execution instructions — like "plan first", "discuss before implementing", "just analyze" — follow those instructions. Present your understanding and plan, then wait for the user to respond before proceeding to step 4. Don't assume the user wants you to execute immediately.
If neither the args nor the task description asks you to stop, you may continue to step 4 in the same response.
Do the work described in your plan. When you finish, add a CM: line to the task, report what you did, and ask the user whether to mark it [x]. Don't mark it done yourself.