Turn a written brief into a ready Teamwork.com task list

**Objective:** Break the brief below into tasks and create them in a task list named {tasklist-name} in the Teamwork project matching {project-name}, finishing by {due-by} when given.

Brief: {brief}

**Step 1: Identify the project**

Call `teamwork-get-projects` with `name.contains` set to {project-name}. If nothing matches, say so and stop. If more than one project matches, list them with `project-name`, `company-name` and `status`, ask which one is meant, and stop. Keep the `project-id` for every later call.

**Step 2: Find or plan the task list**

Call `teamwork-get-tasklists` with `project-id` and `name` set to {tasklist-name}. When it exists, keep its `task-list-id` and call `teamwork-get-tasks` with that `task-list-id` so that you do not duplicate tasks already there. When it does not exist, plan to create it.

**Step 3: Draft the plan**

Draft 3 to 15 tasks from the brief. For each: a name that starts with a verb, a one or two sentence description, `estimated-minutes`, `priority` (low, medium or high), and, when {due-by} is given, a `due-date` spread in working order so the last task is due by that date. Skip any task whose name matches one already in the list.

**Step 4: Approve**

Show the plan as a numbered table and say whether the task list will be created or reused. Ask the user to approve it or edit it. Make no write call until they explicitly approve.

**Step 5: Create**

1. Only when the task list does not exist, call `teamwork-create-tasklist` once with `project-id`, `name` and a short `description` from the brief. Take the new id from the response, or read it back with `teamwork-get-tasklists`.
2. Call `teamwork-create-task` once per approved task, in plan order, with `tasklist-id`, `name`, `description`, `estimated-minutes`, `priority` and `due-date` when set.
3. If a create call fails, stop, and report which tasks were created and which were not.

**Step 6: Verify**

Call `teamwork-get-tasks` with the `task-list-id` and confirm every approved task is there. Report the list with each `task-id`.

**Rules & Guidelines:**

* The only write tools this prompt may call are `teamwork-create-tasklist` (at most once) and `teamwork-create-task` (once per approved task).
* Tasks are created unassigned: no tool here sets assignees. Say so in the final report.
* Do not call `teamwork-update-task`, `teamwork-reorder-tasks`, `teamwork-update-tasklist` or `teamwork-create-milestone`.
* Do not retry a failed create automatically. A retry can create a duplicate.

**Validation:**

* When the brief is too thin to produce three concrete tasks, ask for more detail and stop.
* When {due-by} is in the past or not a date, say so and plan without due dates.