drive-approval

# Drive Approval

User approval flow for implementation review during `/drive`. This skill covers the complete approval cycle: requesting approval, handling revision feedback, and handling abandonment.

## 1. Request Approval

After implementing a ticket, present the approval dialog to the user.

**CRITICAL**: This approval MUST happen at the `/drive` command level to ensure proper user interaction.

### When to Use

After implementing a ticket, present approval dialog with:
- `title` - Ticket title from H1
- `overview` - Brief summary from Overview section
- `changes` - List of changes made during implementation
- `ticket_path` - Path to ticket file

### Approval Prompt Format

```
**Ticket: <title>**
<overview>

Implementation complete. Changes made:
- <change 1>
- <change 2>

[AskUserQuestion with selectable options]
```

### AskUserQuestion Format

**CRITICAL: ALWAYS use selectable `options` parameter. NEVER ask open-ended text questions.**

```json
{
  "questions": [{
    "question": "How would you like to proceed with this ticket?",
    "header": "Approval",
    "options": [
      {"label": "Approve", "description": "Commit and archive this ticket, continue to next"},
      {"label": "Approve and stop", "description": "Commit and archive this ticket, then stop driving"},
      {"label": "Needs revision", "description": "Provide feedback, update ticket, revise implementation"},
      {"label": "Abandon", "description": "Write failure analysis, discard changes, continue to next"}
    ],
    "multiSelect": false
  }]
}
```

**Do NOT proceed to commit until user explicitly approves.**

## 2. Handle Approval and Commit

When user selects "Approve" or "Approve and stop":

1. Follow **write-final-report** skill to update ticket effort and append Final Report section
2. **Verify update succeeded**: If Edit tool fails, halt and report the error to user. DO NOT proceed to archive.
3. Archive and commit using the **archive-ticket** skill:
   ```bash
   bash plugins/core/