---
description: "AirPlan do mode - task executor with UI skill routing"
argument-hint: "[enter|status|finish]"
allowed-tools: "[Read, Glob, Grep, Bash, Write, Edit]"
---

# /do

AirDo is the task executor. It runs individual tasks, enforces routing rules, and integrates with other AirPlan modes.

## Hard Rules

1. **UI Task Handling (P1-20)** — When task involves UI/frontend/interface design:
   - Must detect UI tasks via keyword matching (gui, ui, render, widget, frontend, react, vue, etc.)
   - Must ensure frontend-design Skill is available before executing UI code
   - If frontend-design Skill is not installed, block the task
   - Use `ensure_frontend_design_skill()` and `route_ui_task()` functions

2. **Evidence Gate (INV-4)** — Tasks with GUI/network indicators must have corresponding evidence before finishing:
   - GUI tasks require screenshot/validation evidence
   - Network tasks require packet capture/connectivity evidence
   - Code tasks require static analysis/test results

3. **Force AirDbg Routing (INV-4)** — If task finishes without evidence, force route to AirDbg:
   - `done` status + no validations/files_changed → route to airdbg
   - `blocked`/`failed` status → always route to airdbg

## Sub-commands

### enter

```bash
python "$HOME/plugins/airplan/scripts/airplan.py" --mode do --project . --sub enter --task-id T-001 --task-text "实现登录界面UI"
```

### status

```bash
python "$HOME/plugins/airplan/scripts/airplan.py" --mode do --project . --sub status
```

### finish

```bash
python "$HOME/plugins/airplan/scripts/airplan.py" --mode do --project . --sub finish --task-id T-001 --result /path/to/result.json
```

## UI Task Detection Keywords

UI task detection uses these keywords (case-insensitive):
- gui, ui, render, layout, dialog, osd, overlay, visual
- widget, pane, toolbar, settings_dialog, canvas, button
- window, popup, menu, drm, kms, opengl, vulkan
- frontend, react, vue, angular, web, css, html