karea_create_subtask
Create a subtask under an existing parent task using its visual ID, name, or UUID. Supports deadlines, tags, priority, and session linking.
Instructions
Create a subtask under a parent task. Accepts the parent by visual ID (e.g. KPL77), name, or UUID. Supports the same params as karea_create_task.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sla | No | Deadline: 2d, 5h, tomorrow, monday | |
| tags | No | Tags to attach. STRICT: only pass tags that already exist in this project (verify with karea_view_task or the project list). Do NOT invent new tags unless the user explicitly asked for one — a typo or a paraphrase spawns duplicate tags. When unsure, omit and ask the user. | |
| title | Yes | Subtask title | |
| parent | Yes | Parent task name, visual ID (KPL77, C1), or UUID | |
| source | No | Where this subtask came from | |
| category | No | Category name (defaults to the parent's category if omitted) | |
| markdown | No | Long-form markdown content — investigation findings, technical/functional docs, solution design, root cause analysis. | |
| priority | No | Priority 1-5 (1=critical) | |
| toolType | No | Optional: your AI provider ("claude-code" / "opencode" / "codex" / "cursor" / "aider" / "other"). Required when aiSessionId is supplied. | |
| projectId | No | Project name or ID (needed if parent is a visual ID) | |
| aiSessionId | No | Optional: your current AI CLI session ID. When paired with toolType, atomically links this session to the affected task (equivalent to calling karea_link_session, but saves the round-trip). For Claude Code use the id from `claude --resume`. | |
| description | No | Subtask description. Rendered as Markdown - use `**bold**`, lists, `code`, links, etc. Keep it short. | |
| jiraIssueKey | No | JIRA issue key to link (e.g. PROJ-123). Issue must exist in JIRA. | |
| sessionLabel | No | Optional short label for the linked session (e.g. "Feature draft"). | |
| closingRequisites | No | Requirements that must be met before closing. Keep each one short and concrete - 1 short sentence, ideally under ~120 chars (e.g. "Tests pass in CI", "PR approved"). Do NOT write paragraphs. |