aitask-pickrem-remotelisted

## Overview This skill is a fully autonomous version of `aitask-pick` + `task-workflow` designed for environments where `AskUserQuestion` does not work (e.g., Claude Code Web). It combines task selection and implementation into a single self-contained workflow with **zero interactive prompts**. All decisions are driven by an execution profile. **Key differences from `aitask-pick`:** - Task ID is a **required** argument (no interactive browsing/selection) - No `AskUserQuestion` calls anywhere in the workflow - No worktree/branch management (always works on current branch) - Auto-commits after implementation (no user review loop) - Profile is required and auto-selected (not prompted) ## Arguments **Required:** Task ID (first positional argument) - Format 1: Parent task number (e.g., `42`) - Format 2: Child task ID (e.g., `42_2`) **IMPORTANT:** This skill will NOT work without a task ID argument. If invoked without one, display an error and abort. ## Workflow ### Step 0a: Initialize Data Branch (if needed) Ensure the aitask-data worktree and symlinks are set up: ```bash ./.aitask-scripts/aitask_init_data.sh ``` This is a no-op for legacy repos and already-initialized repos. Required for Claude Code Web where `ait setup` has not been run. Parse stdout: - `INITIALIZED` — Display: "Data branch initialized." Proceed. - `ALREADY_INIT` / `LEGACY_MODE` / `NO_DATA_BRANCH` — Proceed silently. If the command fails (non-zero exit), display the error and abort. ### Step 2: Reso