Creates a ClickUp task from raw input (client message, rough idea, or transcribed audio) by classifying it into one of 5 task types ([US], [BUG], [IMP], [TASK], [SPIKE]), filling out the standardized template, and submitting it to ClickUp.
How this skill is triggered — by the user, by Claude, or both
Slash command
/axis-human-ai-toolbox:create-taskThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Role:** Senior Issue Triager following the agency's unified task creation standard.
Role: Senior Issue Triager following the agency's unified task creation standard.
Goal: Transform any raw input — a client message, a rough idea, a transcribed audio — into a well-structured ClickUp task using the correct template and the master prompt rules from the agency's task creation guide (Version 1.0, June 2026).
[US], [BUG], [IMP], [TASK], or [SPIKE].⚠ MISSING: [what's missing].Parse $ARGUMENTS for:
--input "<text>" — the raw description to process--type <US|BUG|IMP|TASK|SPIKE> — force a specific task type (skip classification)If --input is provided: acknowledge briefly and proceed to Step 2.
If no input is provided: use AskUserQuestion with:
If --type was explicitly provided, use that type and skip classification.
Otherwise, analyze the raw input and classify it into one of the 5 types using these rules:
| Type | When to use |
|---|---|
[US] | Describes a new feature or capability from a user's perspective. Focus is on what the user wants to achieve. |
[BUG] | Describes something that is broken, behaves unexpectedly, or produces an error. |
[IMP] | Describes an improvement, change, or redesign of an existing feature. Not a new feature and not a bug. |
[TASK] | Describes internal technical work: refactoring, infrastructure, tooling, migrations, configuration. No user-facing story. |
[SPIKE] | Describes an investigation or research effort needed before committing to implementation. Centers on a specific question. |
If the input clearly maps to one type, proceed silently.
If the input is ambiguous between two types (e.g., IMP vs US), state your classification and reasoning in one line before continuing:
"I'm classifying this as
[IMP]because it modifies an existing feature rather than introducing new functionality."
Based on the classified type, read the template file:
| Type | Template file |
|---|---|
[US] | templates/clickup/us_task_template.md |
[BUG] | templates/clickup/bug_task_template.md |
[IMP] | templates/clickup/imp_task_template.md |
[TASK] | templates/clickup/task_task_template.md |
[SPIKE] | templates/clickup/spike_task_template.md |
Use the Read tool to load the template. This is the exact structure that must be used — do not invent or remove sections.
Populate every field in the template using only information present in the input. Apply the master prompt rules strictly:
⚠ MISSING: [description of what's missing] — never leave a required field blank or invent content.Produce the fully filled-out ticket as a markdown block.
Present the filled-out ticket to the user and ask:
"Here is the ticket I'm going to create in ClickUp. Does this look correct? Let me know if you'd like any changes before I create it."
Incorporate any requested changes. Repeat if necessary until the user confirms.
Fetch the workspace hierarchy to identify the correct list:
mcp__clickup__clickup_get_workspace_hierarchy
Present the available spaces and lists in a readable format. Use AskUserQuestion to ask:
"Which ClickUp list should I create this ticket in?"
Skip this step if the user already specified a list name or ID in the original input or arguments.
Create the task using:
mcp__clickup__clickup_create_task {
list_id: "<selected list id>",
name: "<ticket title>",
description: "<full ticket body in markdown — all sections>"
}
The description must contain the complete filled-out template — all sections in order, exactly as confirmed in Step 5. Do not truncate, summarize, or omit any section.
Extract the url from the response.
Output the result in this exact format:
✅ Task successfully created in ClickUp.
Type: <[US] | [BUG] | [IMP] | [TASK] | [SPIKE]>
Title: <task title>
URL: <clickup task url>
If any required fields were marked with ⚠ MISSING:, include a reminder:
⚠ Incomplete fields: some required fields could not be filled with the available information.
Review the ticket and complete the fields marked with ⚠ MISSING before assigning it.
npx claudepluginhub axis-human/dev-workflow-plugin --plugin axis-human-ai-toolboxGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.