Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From task
This skill should be used when the user mentions "ClickUp task", "CU-xxx", "task workflow", "clickup integration", or when working with task plugin commands (/task:start, /task:done, /task:merge, /task:status, /task:new). Provides workflow patterns for ClickUp task management integrated with kas.
npx claudepluginhub kastheco/claude-plugins --plugin taskHow this skill is triggered — by the user, by Claude, or both
Slash command
/task:task-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides workflow patterns for managing ClickUp tasks integrated with kas workflow commands. The core principle: **delegate all ClickUp API calls to the clickup-task-agent** to keep the main conversation context clean.
Manages ClickUp tasks via API v2: create, read, update, delete with assignees, priorities, due dates, subtasks, statuses, tags, and custom fields. Triggers on 'clickup task' phrases.
Guides users through task manager setup: pick manager (Linear/Jira/GitHub Issues/Notion), integration method (MCP/CLI/plugin/API), verify, and write helper skill. Part of /process-setup.
Transitions ClickUp task to In Progress, displays name status assignees checklist and link, adds start comment, assigns to user if unassigned. Use /start #taskID to begin work.
Share bugs, ideas, or general feedback.
This skill provides workflow patterns for managing ClickUp tasks integrated with kas workflow commands. The core principle: delegate all ClickUp API calls to the clickup-task-agent to keep the main conversation context clean.
NEVER call ClickUp MCP tools directly in main context.
All ClickUp operations delegate to the clickup-task-agent subagent which returns concise summaries. This prevents verbose API responses from polluting the conversation.
| /task Command | Skills/Commands Used | ClickUp Actions |
|---|---|---|
/task:start CU-xxx | superpowers:brainstorming → kas:review-plan (loop) → superpowers:subagent-driven-development OR superpowers:executing-plans | Fetch task, set "in progress", assign |
/task:done | /kas:verify → /kas:done → PR | Set "ready for review", comment PR |
/task:merge | /kas:merge | Set "complete" |
/task:status [id] | None | Fetch and display status |
/task:new | None | Create task via interview |
/task:start uses superpowers-driven planning:
superpowers:brainstorming - explores, asks questions, outputs designkas:review-plan - max 5 iterations until APPROVED or user overrides/abortssuperpowers:subagent-driven-development (same session)superpowers:executing-plans (separate session with worktree)Activate this skill when detecting:
https://app.clickup.com/t/...CU-xxx, #xxx, task xxxWhen needing ClickUp data, spawn the clickup-task-agent:
Task tool with subagent_type="task:clickup-task-agent":
"[Operation description]
1. [MCP tool call 1]
2. [MCP tool call 2]
Return ONLY: [concise format]"
The agent uses haiku model for speed and returns formatted summaries.
feat/CU-<id>-<slug> or fix/CU-<id>-<slug>CU-<task-id> for ClickUp linking[CU-xxx] prefix| Scenario | Action |
|---|---|
| Fetch fails at start | Stop, show error, suggest retry |
| Status update fails after kas success | Warn user, show manual command |
| kas command fails | Stop, do NOT update ClickUp |
Partial failures: If kas succeeds but ClickUp API fails, warn user and provide manual update command. Don't fail the entire operation for ClickUp sync issues.
For detailed patterns and prompts:
references/subagent-prompts.md - Copy-paste subagent prompts for each operationreferences/setup.md - ClickUp authentication setupreferences/task-templates.md - Task description templates