solve-tasklisted

# Solve Task Gather the right context for a task, distill it into a brief, then enter the normal development workflow. This skill does NOT plan or implement — it disciplines context-gathering and hands the brief to `superpowers:brainstorming` (which leads to writing-plans → subagent-driven-development, or the execution strategy chosen in the startup survey (inline / subagent / lite)). ## Inputs `$ARGUMENTS` is either: - a task key (e.g. `PRI-4`, matching the board's `key_pattern`), or - a free-text description (e.g. "add a logout endpoint"). ## Pipeline 0. **Startup: survey + Preflight (index freshness + task-corpus warm-up).** Run this BEFORE anything else. First resolve, once, the repo path (`git rev-parse --show-toplevel`) and the working branch (`git branch --show-current`; if it is in `REVIEW_BRANCHES` use it, else the primary branch) — step 3 reuses the same branch for `search_codebase`. **Resolve `task_board` exactly once before any board call.** Read the repo `.review.yml` block: its `task_board` mapping has priority; an absent block falls back to `get_board_config()`; an explicit empty `task_board:` disables board work for this run. Keep the resolved `{type, project, key_pattern, create_target, done_target, options}` value and **reuse this resolved value** in Step 1 and every board operation. Never call the deploy fallback when the repo explicitly disables the board. **Call `prepare_task_context(repo, key, branch, warm_board=True)` o