How do I install the Clickup Task Workflow skill?

Run npx skillmds@latest add tomevault-io/clickup-task-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clickup Task Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clickup Task Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clickup Task Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clickup Task Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clickup Task Workflow by tomevault-io

Name: Clickup Task Workflow
Author: tomevault-io

Clickup Task Workflow

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. Use when this capability is needed.

tomevault-io fa01cd1 2 files · 4.4 KB Updated Sep 17, 2026

File contents

ClickUp Task Workflow

Overview

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.

Core Principle

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.

Command Mapping

/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

Planning Workflow

/task:start uses superpowers-driven planning:

Fetch task via clickup-task-agent (capture original status for rollback)
Enter plan mode using EnterPlanMode tool
Brainstorming via superpowers:brainstorming - explores, asks questions, outputs design
Review loop via kas:review-plan - max 5 iterations until APPROVED or user overrides/aborts
Implementation via user choice:
- Option 1: superpowers:subagent-driven-development (same session)
- Option 2: superpowers:executing-plans (separate session with worktree)

Detection Triggers

Activate this skill when detecting:

Task References

URLs: https://app.clickup.com/t/...
Task IDs: CU-xxx, #xxx, task xxx
Work phrases: "work on", "implement", "fix task", "start on"

Task Creation

Creation phrases: "create task", "new feature", "log bug", "file issue"

Subagent Delegation Pattern

When 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.

Git Conventions

Branch naming: feat/CU-<id>-<slug> or fix/CU-<id>-<slug>
Commit messages: Include CU-<task-id> for ClickUp linking
PR titles: Include [CU-xxx] prefix

Error Handling

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.

Additional Resources

Reference Files

For detailed patterns and prompts:

references/subagent-prompts.md - Copy-paste subagent prompts for each operation
references/setup.md - ClickUp authentication setup
references/task-templates.md - Task description templates

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: clickup-task-workflowdescription: 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. Use when this capability is needed.---# ClickUp Task Workflow## OverviewThis 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.## Core Principle**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.## Command Mapping| /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 |## Planning Workflow`/task:start` uses superpowers-driven planning:1. **Fetch task** via clickup-task-agent (capture original status for rollback)2. **Enter plan mode** using EnterPlanMode tool3. **Brainstorming** via `superpowers:brainstorming` - explores, asks questions, outputs design4. **Review loop** via `kas:review-plan` - max 5 iterations until APPROVED or user overrides/aborts5. **Implementation** via user choice: - Option 1: `superpowers:subagent-driven-development` (same session) - Option 2: `superpowers:executing-plans` (separate session with worktree)## Detection TriggersActivate this skill when detecting:### Task References- **URLs**: `https://app.clickup.com/t/...`- **Task IDs**: `CU-xxx`, `#xxx`, `task xxx`- **Work phrases**: "work on", "implement", "fix task", "start on"### Task Creation- **Creation phrases**: "create task", "new feature", "log bug", "file issue"## Subagent Delegation PatternWhen 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.## Git Conventions- **Branch naming**: `feat/CU-<id>-<slug>` or `fix/CU-<id>-<slug>`- **Commit messages**: Include `CU-<task-id>` for ClickUp linking- **PR titles**: Include `[CU-xxx]` prefix## Error Handling| 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.## Additional Resources### Reference FilesFor detailed patterns and prompts:- **`references/subagent-prompts.md`** - Copy-paste subagent prompts for each operation- **`references/setup.md`** - ClickUp authentication setup- **`references/task-templates.md`** - Task description templates---> Converted and distributed by [TomeVault](https://tomevault.io/claim/kastheco) — claim your Tome and manage your conversions.

Frequently asked questions