create_task
Create structured tasks with Jira-like IDs, dependencies, priorities, and metadata to manage project workflows and execution order.
Instructions
Creates a new task with YAML frontmatter metadata. Uses Jira-like IDs (e.g., AUTH-001, API-042) for stable references. Supports dependencies, priorities, estimates, due dates, and tags. Agents can determine execution order by checking dependencies and priorities.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | The title of the task (e.g., "Implement OAuth authentication", "Fix login bug"). | |
| project | Yes | Project/Epic identifier used in the task ID (e.g., "AUTH", "API", "FRONTEND"). Will be uppercased. The task ID will be {PROJECT}-{NNN}. | |
| description | No | Detailed description of the task. Can include markdown formatting. | |
| owner | No | Who is responsible for this task (e.g., "cursor", "john-doe", "backend-team"). | |
| priority | No | Priority level: "P0" (critical/blocker), "P1" (high), "P2" (medium/default), "P3" (low). | P2 |
| status | No | Current status: "todo" (not started), "in_progress" (being worked on), "blocked" (waiting on something), "review" (needs review), "done" (completed). | todo |
| depends_on | No | Array of task IDs this task depends on (e.g., ["AUTH-001", "AUTH-002"]). Task cannot start until dependencies are done. | |
| blocked_by | No | Array of task IDs or external blockers (e.g., ["AUTH-003", "waiting-on-api-key"]). Different from depends_on - these are blockers that prevent progress. | |
| estimate | No | Time estimate (e.g., "2h", "1d", "3d", "1w"). Use h=hours, d=days, w=weeks. | |
| due | No | Due date in YYYY-MM-DD format (e.g., "2025-01-15"). | |
| tags | No | Array of tags for categorization (e.g., ["security", "urgent", "tech-debt", "feature"]). | |
| subtasks | No | Array of subtask descriptions. Will be rendered as a checklist in the task. |