# Tasks Review Process

Review generated task list before converting to bd issues.

## When to Use

After `/speckit.tasks` generates tasks, before `bd create`. Once tasks become issues, you're committed to the breakdown.

## 1. Locate the Tasks

```bash
BRANCH=$(git branch --show-current)
TASKS_FILE="specs/${BRANCH}/tasks.md"

if [[ ! -f "$TASKS_FILE" ]]; then
  echo "Error: $TASKS_FILE not found. Run /speckit.tasks first." >&2
  return 1
fi
```

Also load plan for context:
```bash
PLAN_FILE="specs/${BRANCH}/plan.md"
```

## 2. Run the Review

```bash
orch consensus --mode critique --temperature 0.7 \
  --file "$TASKS_FILE" \
  --file "$PLAN_FILE" \
  "$(cat ~/.claude/skills/spec-review/prompts/tasks-review.txt)" \
  flash deepseek gpt
```

**Why these settings**:
- `--mode critique` - Find problems with the breakdown
- `--temperature 0.7` - Balanced creativity
- Include plan for context on what tasks should accomplish

## 3. What to Look For

**Granularity issues**:
- Tasks too large (should be split)
- Tasks too small (should be combined)
- Missing tasks (gaps in coverage)

**Dependency issues**:
- Wrong ordering
- Missing dependencies
- Circular dependencies

**Scope issues**:
- Tasks that don't trace to plan
- Gold-plating (unnecessary tasks)
- Missing edge case handling

**Clarity issues**:
- Vague task descriptions
- Unclear acceptance criteria
- Ambiguous ownership

## 4. Next Steps

| Result | Action |
|--------|--------|
| Major issues | Revise tasks, re-run review |
| Minor tweaks | Fix before bd create |
| Clean | Ready for `bd create` |

## Why Review Before bd create?

- Easier to restructure tasks in markdown than in issue tracker
- bd issues carry history - better to get it right first
- Dependencies in bd are harder to refactor than in a task list
