review-workflow-design

# Review Workflow Design Skill

Design review workflows that validate implementation against specifications with visual proof.

## When to Use

- Setting up review processes for features
- Creating proof-of-value workflows
- Designing spec-based validation
- Implementing auto-resolution loops

## Core Concept

Review answers: **"Is what we built what we asked for?"**

This is different from testing which answers: "Does it work?"

## Design Workflow

### Step 1: Define Spec Location Pattern

Establish where specifications live:

```text
specs/
├── feature-{name}.md
├── bug-{name}.md
└── chore-{name}.md
```

Or:

```text
specs/issue-{number}-{type}.md
```

### Step 2: Design Screenshot Capture Points

Identify critical paths that need visual proof:

1. **Initial State**: Before any interaction
2. **Key Actions**: After significant user actions
3. **Final State**: End result of the feature

Example:

```text
1. Take screenshot of dashboard (initial state)
2. Click "Export" button
3. Take screenshot of export modal
4. Complete export
5. Take screenshot of success message
```

### Step 3: Define Severity Classification

Configure issue severity levels:

| Severity | Criteria | Action |
| --- | --- | --- |
| **blocker** | Prevents release, harms UX | Auto-resolve |
| **tech_debt** | Quality issue, works | Document |
| **skippable** | Polish, preference | Ignore |

### Step 4: Set Up Resolution Workflow

Design the auto-resolution loop:

```text
Review
  ├── Issues found?
  │     ├── Blockers? → /patch → /implement → Re-review
  │     └── No blockers → Success
  └── No issues → Success

Maximum 3 retry attempts
```

### Step 5: Configure Proof Storage

Options for screenshot storage:

- **Local**: `agents/{adw_id}/review_img/`
- **Cloud**: R2, S3, or similar (public URLs)
- **Git**: Committed with review artifacts

## Review Command Structure

```markdown
# Review Implementation Against Spec

## Variables
spec_file: $1

## Instructions

1. **Read Specification**
   - Under