resolve-blocker

# Resolve Blocker Skill

!`node $SAGA_PLUGIN_ROOT/scripts/find.js "$0" --type story`

## Process

### 1. Check Resolution Result

The `saga find` command ran above. Handle the result:

- **If found=true**: Extract `data.slug` and `data.epicSlug`, continue to step 2
- **If found=false with matches array**: Use AskUserQuestion to disambiguate:
  ```
  question: "Which story's blocker do you want to resolve?"
  header: "Story"
  multiSelect: false
  options: [
    {label: "<slug>", description: "<title> (Epic: <epicSlug>, Status: <status>)"}
    ...for each story in the matches array
  ]
  ```
  After selection, continue with the selected story.
- **If found=false with error**: Display the error. Suggest using `/task-list` to see available stories.

### 2. Locate Story Files

Compute paths to story files:
```
EPIC_SLUG=<epic_slug from resolution>
STORY_SLUG=<story_slug from resolution>
WORKTREE="$SAGA_PROJECT_DIR/.saga/worktrees/$EPIC_SLUG/$STORY_SLUG"
STORY_DIR=".saga/epics/$EPIC_SLUG/stories/$STORY_SLUG"
```

Story files within the worktree:
- `$WORKTREE/$STORY_DIR/story.md` - Story definition
- `$WORKTREE/$STORY_DIR/journal.md` - Execution journal

### 3. Read Story Context

Read the story definition to understand what's being built:

```bash
cat $WORKTREE/$STORY_DIR/story.md
```

Extract:
- Story title and context
- Tasks and their guidance
- References and patterns

### 4. Read Journal and Find Blocker

Read the journal to find the blocker:

```bash
cat $WORKTREE/$STORY_DIR/journal.md
```

A blocker entry has this format:

```markdown
## Blocker: [Brief title]

**Task**: [Which task is blocked]
**What I'm trying to do**: [Description]
**What I tried**: [Approaches attempted and why they didn't work]
**What I need**: [Specific decision or information required]
**Suggested options**: [If ideas exist, list them with pros/cons]
```

A resolution entry has this format:

```markdown
## Resolution: [Reference to blocker title]

**Decision**: [Clear statement of the chose