harness

# /harness Skill

Transform a Claude Code plan into an execution config for `mizu execute`.

## Usage

```
/harness                                    # Auto-detect recent plans
/harness ./.mizu/plans/2024-01-15-feature.md # Specific plan file
```

## Workflow

### Step 1: Find the Plan

**With argument:** Use that file directly.

**Without argument:** Scan `.mizu/plans/` for `.md` files. If multiple, use AskUserQuestion to let user choose.

### Step 2: Extract Tasks

**Try structured parsing first.** Look for numbered lists under:
- `## Implementation Steps`
- `## Tasks`
- `## Plan`

Parse: `1. Do something` → task

**If no standard format:** Use AI to extract tasks, then confirm with user via AskUserQuestion.

### Step 3: Infer Permissions

Start with `dev` preset. Analyze plan for keywords:

| Keywords | Add to inferred |
|----------|-----------------|
| docker, container | `docker` |
| database, postgres, psql | `psql` |
| aws, s3 | `aws` |

Show inferred permissions to user for confirmation.

### Step 4: Infer Verification Commands

| Task Pattern | Verification |
|--------------|--------------|
| "add tests", "write tests" | `bun test` |
| "fix build", "update build" | `bun run build` |
| "typecheck", "create types", "add types", "schema" | `bun run typecheck` |
| "lint", "fix lint" | `bun run lint` |

Leave as `null` for ambiguous tasks (worker self-verifies).

### Step 4b: Set Dependencies

**Default:** Make tasks sequential (each depends on previous).
- `task-001`: no dependencies
- `task-002`: depends on `["task-001"]`
- `task-003`: depends on `["task-002"]`

**Exception:** If tasks are clearly independent (e.g., "update docs" and "add tests" for different modules), they can run in parallel with same dependencies.

### Step 5: Generate Config

**CRITICAL FORMAT REQUIREMENTS:**

```json
{
  "version": "1.0.0",
  "planFile": "./<filename>.md",
  "projectDir": "/absolute/path/to/project",
  "model": "claude-sonnet-4-5",
  "tasks": [
    {
      "id": "task-00