en un clic
agkan-add
Use when adding a new task to the backlog — collects title, body, tags, priority, and parent task, then creates it with agkan.
Menu
Use when adding a new task to the backlog — collects title, body, tags, priority, and parent task, then creates it with agkan.
Use when managing tasks with the agkan CLI tool - creating, listing, updating tasks, managing tags, blocking relationships, or tracking project progress with the kanban board.
Use when reviewing backlog tasks to assess decomposition, implementation readiness, and priority ordering before development begins.
Use when starting a development session to pick the highest priority Todo task from agkan, implement it directly without PR/branch, and mark it done.
Use when starting a development session to pick the highest priority Todo task from agkan, implement it, create a pull request, and mark it done.
Use when a task has been selected and you need to implement it directly without PR/branch creation - handles in_progress update, implementation, and marking done.
Use when a task has been selected and you need to implement it in an isolated (forked) context - handles in_progress update, branch creation, implementation, PR creation, and marking review.
| name | agkan-add |
| description | Use when adding a new task to the backlog — collects title, body, tags, priority, and parent task, then creates it with agkan. |
A workflow to add a new task to the backlog with all relevant fields set in one pass.
Gather the following from the user. Fields marked optional can be skipped if not provided.
| Field | Required | Notes |
|---|---|---|
| Title | Yes | Short, descriptive task title |
| Body | No | Detailed description, background, acceptance criteria |
| Tags | No | One or more from the canonical tag list (see below) |
| Priority | No | critical / high / medium / low (default: medium) |
| Parent task ID | No | ID of an existing task to nest this task under |
| Branch | No | Branch name to assign (stored in branch column); leave blank to auto-generate at implementation time |
Use AskUserQuestion to collect all fields in one pass. Include Title, Body, Tags, Priority, Parent, and Branch in your question set.
When the user provides a Branch value → include --branch <name> in the agkan task add command.
When the user leaves Branch blank → omit --branch; the branch will be auto-generated by agkan-subtask or agkan-subtask-direct at implementation time.
Canonical tag list (in priority order):
| Tag | Use when |
|---|---|
bug | Something is broken |
security | Security-related concern |
improvement | Enhancement to existing functionality |
test | Test coverage or QA |
performance | Speed or resource optimization |
refactor | Code quality, no behavior change |
docs | Documentation |
Single-line body: Pass directly as an argument.
agkan task add "<title>" "<body>" --priority <value>
agkan task add "<title>" --priority <value> # no body
agkan task add "<title>" "<body>" # medium priority (default, flag omitted)
agkan task add "<title>"
agkan task add "<title>" "<body>" --branch <branch> # with branch
agkan task add "<title>" --branch <branch> # no body, with branch
Multi-line body: MUST use --file.
Write the body to a temporary file first, then pass it with --file. NEVER use $'...' syntax or \n in arguments for multi-line content.
# Step 1: Write body to a temp file (use Write tool)
# /tmp/task_body.md:
# 1行目
# 2行目
#
# ## 詳細
# 内容はここに
# Step 2: Create task with --file
agkan task add "<title>" --file /tmp/task_body.md
# Step 3: Delete the temp file
rm /tmp/task_body.md
Note the task ID returned from the command output.
For each tag:
agkan tag attach <task-id> <tag-name>
agkan task update-parent <task-id> <parent-id>
If this task depends on other tasks (i.e., cannot start until another task is done), set the blocking relationship.
<blocker-id> is the task that must complete first<blocked-id> is the new task being addedagkan task block add <blocker-id> <task-id>
Ask the user whether there are any tasks this new task is blocked by, or any tasks this new task blocks.
Retrieve and display the created task:
agkan task get <task-id>
Output a concise summary to the user:
backlog)backlog status by defaultready — that is handled by agkan-planning