iw-executelisted

# Execute Work Item Workflow Execute the AI development workflow for work item **$ARGUMENTS**. **Argument parsing:** `$ARGUMENTS` may contain `ITEM_ID STEP_ID` (e.g. `CR-00003 S03`) when invoked by the daemon. - **ITEM_ID** = first token (e.g. `CR-00003`) - **STEP_ID** = second token if present (e.g. `S03`) — use to resume from that step ## Pre-Flight Data Current status from platform: !`uv run iw item-status $(echo $ARGUMENTS | awk '{print $1}') --json 2>/dev/null || echo '{"error": "item not found or not registered"}'` Work item design document location: !`ls -d ai-dev/active/$(echo $ARGUMENTS | awk '{print $1}') 2>/dev/null || echo "NOT_FOUND: $(echo $ARGUMENTS | awk '{print $1}') not in ai-dev/active/"` ## Pre-Flight Validation Parse `$ARGUMENTS` into `ITEM_ID` (first token) and optional `STEP_ID` (second token). Use only `ITEM_ID` for all `iw` CLI commands below. Before executing, validate: 1. **Item is registered** — `uv run iw item-status ITEM_ID` must succeed 2. **Item status is `approved`** — if `draft`, tell user to run `uv run iw approve ITEM_ID` first 3. **Design doc exists** — must be in `ai-dev/active/ITEM_ID/` ## If item not found: Report error: "Work item ITEM_ID not found in database. Create a design first with /iw-new-feature, /iw-new-incident, or /iw-new-cr, then register it with `uv run iw register`." ## If item status is `draft`: Report: "Work item ITEM_ID is in 'draft' status. Review the design, then approve with: `iw approve ITEM_ID`" ## I