Move your Vibe Kanban, Beads, Backlog.md or Taskmaster tasks into Taskhold

sqlite3 -readonly -json "$HOME/Library/Application Support/ai.bloop.vibe-kanban/db.v2.sqlite" \
  "SELECT p.name AS project, t.title, t.description, t.status
     FROM tasks t JOIN projects p ON p.id = t.project_id
    WHERE t.status NOT IN ('done', 'cancelled')
    ORDER BY t.created_at" > vibe-tasks.json

Move the Vibe Kanban tasks in vibe-tasks.json into Taskhold.

- Each entry is one open task. Call taskhold_create for each:
  - project: the entry's project (the Vibe Kanban project name)
  - title: title
  - description: description, then a last line "From Vibe Kanban, status <status>"
  - labels: ["in-review"] when status is inreview
- Leave priority out (Vibe Kanban's local tasks have none, so they come in as medium).
- Don't start any task.
- When you finish, tell me how many tasks you filed per project.

Move the open issues in issues.csv (a Vibe Kanban export) into Taskhold.

- Skip issues with a Completed date, and issues whose Status is a done or canceled column.
- An issue with a Parent Issue becomes a step of its parent's task. Every other open issue becomes a task.
- For each task, call taskhold_create:
  - project: the Project column
  - title: Title
  - description: Description, then "Due <Due Date>" if there is one, then a last line "Vibe Kanban <Issue ID>, status <Status>"
  - priority: Urgent = urgent, High = high, Medium = medium, Low = low, empty = medium
- Then, for a task with child issues, call taskhold_plan with task_id (the new task's id) and steps: one {title, description} per child, oldest first.
- Don't start any task.
- When you finish, tell me how many tasks and steps you filed and how many issues you skipped.

bd export -o beads.jsonl

Move the open Beads issues in beads.jsonl into Taskhold.

- Project: this repo's folder name. Pass it as project on every call.
- Each line is one issue. Skip issues whose status is closed.
- An issue with a "parent-child" dependency is a child, and depends_on_id is its parent. Children of an open parent become steps of the parent's task. Every other open issue becomes a task.
- For each task, call taskhold_create:
  - title: title
  - description: description, then design and acceptance_criteria under their own headings when present, then "Waits on: <depends_on_id, ...>" for its "blocks" dependencies, then a last line "Beads <id>, status <status>"
  - priority: 0 = urgent, 1 = high, 2 = medium, 3 or 4 = low
  - labels: labels plus issue_type, up to 20
- Then, for a task with children, call taskhold_plan with task_id (the new task's id) and steps: one {title, description} per child in id order (bd-a3f8.1 before bd-a3f8.2), each description being the child's description plus "Beads <id>". Grandchildren go in the same list, after their parent.
- For each comment on an issue, call taskhold_add_note on its task with "<author>: <text>".
- Don't start any task, and don't run bd commands that change anything.
- When you finish, tell me how many tasks and steps you filed and how many issues you skipped.

Move the open Backlog.md tasks into Taskhold.

- Project: this repo's folder name. Pass it as project on every call.
- Read the .md files in backlog/tasks/. Leave out backlog/completed/, backlog/archive/ and backlog/drafts/.
- Skip tasks in the final status (the last entry of statuses in backlog/config.yml, Done by default).
- A file with parent_task_id is a subtask and becomes a step of its parent's task. Every other open file becomes a task.
- For each task, call taskhold_create:
  - title: title
  - description: the Description section, then the unchecked Acceptance Criteria items ("- [ ]"), then the Implementation Plan if there is one, then "Depends on <dependencies>" when that list isn't empty, then a last line "Backlog.md <id>: <file path>". Leave out the <!-- ... --> marker comments.
  - priority: priority (medium if missing)
  - labels: labels, up to 20
- Then, for a task with open subtasks, call taskhold_plan with task_id (the new task's id) and steps: one {title, description} per subtask in id order, each description being its Description section plus "Backlog.md <id>".
- Don't edit, move or archive any file in backlog/.
- When you finish, tell me how many tasks and steps you filed and how many files you skipped, by status.

Move the Taskmaster tasks in .taskmaster/tasks/tasks.json into Taskhold.

- Project: this repo's folder name. Pass it as project on every call.
- The file has one object per tag, each with a tasks array. If tasks sits at the top level instead, treat it as the master tag.
- Skip tasks and subtasks whose status is done or cancelled.
- For each remaining task, call taskhold_create:
  - title: title
  - description: description, then "Details:" with details, then "Test strategy:" with testStrategy, then "Depends on Taskmaster tasks <dependencies>" when that list isn't empty, then a last line "Taskmaster task <id>, tag <tag>, status <status>". 10,000 characters at most.
  - priority: priority (medium if missing)
  - labels: the tag name unless it is master, plus "deferred" or "review" when that is the status
- Then, for a task with remaining subtasks, call taskhold_plan with task_id (the new task's id) and steps: one {title, description} per subtask in id order, each description being its description and details, 5,000 characters at most.
- Don't start any task, and don't edit tasks.json.
- When you finish, tell me how many tasks and steps you filed and how many you skipped, by status.