board-startlisted

# /board-start Take a ClickUp task from spec to a review-ready PR, in one prompt. This is the "work it" half of the board lifecycle; `/board-ship` is the "ship it" half. ClickUp is the source of truth for task status. GitHub holds the code: the branch and PR carry the `CU-` task id so ClickUp's native integration links the activity back to the task. This skill **does real work**: it writes code. Status changes use the `board-move` logic, but the point is the implementation between them. ## Usage ``` /board-start <task-id> [base-branch] ``` - `task-id`: ClickUp task ID, with or without the `CU-`/`#` prefix (e.g. `CU-86c98x5e6`). - `base-branch` (optional): integration branch to branch from and target the PR at. If omitted, resolve it (step 3). If no task ID is provided, pick one rather than asking. `cu tasks --list <list_id> --json` gives status, priority and tags in one call; take the highest-priority task in the Ready status, and where two tie, take the one whose acceptance criteria you can actually satisfy. **Skip a task whose AC is a decision only the user can make** ("resolve the App Store listing name", "decide whether to sell X"): this skill writes code, and a brand or pricing call sitting at urgent is not a smaller version of that. Say in one line which you took and why, then start. Ask only when nothing in the list is implementable. ## Prerequisites The `cu` CLI must be authenticated (`cu status`). Read `.tasks/config.json` for `list_id`, `status_map`, and th