board-speclisted

# /board-spec Write the PRD before anyone writes code. This is the "spec it" first third of the board lifecycle: `/board-spec` → `/board-start` → `/board-ship`. The Open column holds raw ideas; Ready holds tasks that `/board-start` (or any engineer) can pick up cold and implement without guessing. ClickUp is the source of truth: the PRD lives in the task description, because that is exactly what `/board-start` reads for acceptance criteria. This skill **does not write code**. It reads the codebase to ground the spec in reality, then writes the document. ## Usage ``` /board-spec <task-id> ``` - `task-id`: ClickUp task ID, with or without the `CU-`/`#` prefix. If no task ID is provided, list the board's Open tasks (`cu tasks --list <id> --status Open`) and ask which to spec. ## Prerequisites The `cu` CLI must be authenticated (`cu status`). Read `.tasks/config.json` for `list_id` and `status_map` if present. ## Steps ### 1. Read the raw idea ```bash cu task get <task-id> --json | grep -m1 '^{' # structured fields: status, tags, assignees cu task get <task-id> --markdown # the DESCRIPTION / existing PRD body cu comments list <task-id> ``` The `--json` output of this CLI **omits the description field**: use `--markdown` to read the task body (the raw idea or an existing PRD). Capture the original idea text verbatim. It is preserved at the bottom of the PRD, never overwritten silently. ### 2. Investigate the codebase, and check for prior art Ground