board_create_task
Create a project task with title, status, priority, and optional subtask or dependency links.
Instructions
Create a task in a project. Status defaults to 'todo' and priority to 'medium' if not specified. If the initial status is 'in_progress', started_at is auto-set to now; if 'done', completed_at is auto-set. Writes an activity_log entry for audit. Use parent_task_id to create a subtask under another task (common pattern for decomposing work). Use depends_on to express ordering ('task B blocks on task A'). Returns { id, title, status, priority, message }.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID (from board_get_projects) where this task belongs | |
| title | Yes | Short title — one line, what needs doing. Appears in handoff summaries and task lists. | |
| description | No | Longer details: context, acceptance criteria, file refs, links. Recommended for any task that will outlive the current session. | |
| status | No | Initial status. Default 'todo'. Use 'backlog' for not-yet-prioritized ideas. | |
| priority | No | Priority — drives sort order in board_get_tasks and handoff. Default 'medium'. Reserve 'critical' for blocking issues. | |
| assigned_agent | No | Agent name responsible for this task (free-form string, e.g., 'main', 'code-reviewer', 'database-specialist'). Omit if unassigned. | |
| parent_task_id | No | If this is a subtask, the ID of the parent task. Subtasks inherit no fields from the parent — they just share a parent_task_id link. | |
| depends_on | No | IDs of tasks that must complete before this one can start. The server does not auto-block — this is advisory metadata that callers can check. | |
| riper_mode | No | Which RIPER phase this task belongs to. Useful when tasks span a multi-phase workflow. | |
| metadata | No | Optional key/value metadata (e.g., { file: 'src/foo.ts', line: 42, issue: 'XSS' }). Merged shallowly on board_update_task. |