From cotask
Creates tasks or sections in TASKS.md to track project work. Auto-triggers on phrases like 'add a task', 'todo', 'let's plan', or untracked future work.
npx claudepluginhub wbopan/cotask-marketplace --plugin cotaskThis skill uses the workspace's default tool permissions.
- User's instruction: {{ARGS}}
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.
Creates taskmd task files via CLI: parses user input for title, template, flags like priority/tags/group; fills objective, subtasks, criteria; validates output. Use when adding project tasks.
Interactively scaffolds TASKS.md by collecting project info, analyzing code (package.json/pyproject.toml), and injecting specialist backend/frontend/security tasks. Use at project start or to organize todos.
Share bugs, ideas, or general feedback.
Creates tasks or sections in TASKS.md. The user invoked this command — act immediately, do not ask for confirmation.
Do NOT say: "Should I", "Want me to", "Shall I", "Would you like me to", "Let me know if".
Read TASKS.md (at the project root). If it doesn't exist, create it from the template at ${CLAUDE_PLUGIN_ROOT}/skills/cotask/references/template.md (ask the user for a project title first).
If the task doesn't already exist in the file, write it with Edit. Do not read any other files.
Where to put it: Append at the end of the user-specified section's task list. If no section specified, use the last section that has [ ] or [/] tasks. If there are no sections (tasks live directly under # TASKS), append at the end of the task list.
Status symbols: [ ] todo (default), [/] ongoing, [x] done, [-] backlog. Use [/] if the user wants it done now — then continue as /starting-task.
Task format — each task is a - [status] line with a #slug at the end, followed by indented description and AC: lines. No blank lines between tasks. Example:
- [ ] Fix login page auth bugs #fix-auth-bug
Users intermittently get 403 when logging in with SSO.
AC: SSO login succeeds on all tested providers; no 403 in logs.
- [ ] Add rate limiting to API endpoints #add-rate-limiting
Public endpoints have no throttling, vulnerable to abuse.
AC: Endpoints return 429 after exceeding configured request threshold.
Key rules:
#. Must be unique in the file.AC:. Describes observable outcome, not implementation steps. Use the user's if provided, otherwise write one yourself.Section format — ## Name header followed by an optional Description: paragraph, then tasks:
## Authentication
Description: User login and session management improvements.
- [ ] Fix login page auth bugs #fix-auth-bug
...
When creating a section, suggest 3-5 initial tasks.
One or two lines:
Created
#fix-auth-bug(todo). AC: SSO login succeeds on all tested providers.
If triggered mid-task, resume whatever you were doing before.