Create a single, well-researched kanban task. Use when the user wants to add a task, track an idea, or capture work without entering full plan mode.
{% include "_partials/coding-standards" %} {% include "_partials/task-standards" %}
Create a single, well-researched kanban task from an idea, request, or bug report.
{% if arguments %}
{{arguments}} {% endif %}
{% if arguments %}Start from the user request above.{% endif %} If anything is ambiguous or underspecified, use the question tool to ask clarifying questions before proceeding. A great task requires clear understanding — don't guess.
Use code_context as the primary research tool:
op: "search symbol" with domain keywords, for implementationsop: "get symbol"op: "get blastradius" on files you expect the work to touch. This reveals callers, downstream consumers, tests, and transitive dependencies.op: "get callgraph" with direction: "inbound" and "outbound" to understand execution flowThorough research is always required. The tools you use may differ — a bug fix may focus on blast radius while a feature requires broader symbol exploration — but never skip research because something appears simple.
Create the task on the kanban board using kanban with op: "add task". The task must meet the task standards included above — What, Acceptance Criteria, and Tests sections are mandatory.
If the research reveals the work is too large for a single task (exceeds sizing limits), tell the user and suggest they use /plan instead.
Show the user the task you created — title, description, and any tags applied.
/plan for the rest.question tool to clarify before creating the task.