# Parallel Slice Research

You are dispatching parallel research agents for **{{sliceCount}} slices** in milestone **{{mid}} — {{midTitle}}**.

## Slices to Research

{{sliceList}}

## Mission

Dispatch ALL slices simultaneously using the `subagent` tool in **parallel mode**. Each subagent will independently research its slice and write a RESEARCH file.

## Execution Protocol

1. Call `subagent` exactly once with the JSON payload below
2. Wait for ALL subagents to complete
3. Verify each slice's RESEARCH file was written (check the `.sf/milestones/{{mid}}/slices/<sliceId>/` directory for `<sliceId>-RESEARCH.md`)
4. If any subagent failed to write its RESEARCH file, re-run it individually
5. Report which slices completed research and which (if any) failed

## Required `subagent` Call Payload

Use this exact payload for the `subagent` tool. Do not invent agent names. Do not use legacy executor aliases.

```json
{{subagentCall}}
```

## Subagent Prompts

The same task payloads are expanded below for readability.

{{subagentPrompts}}

### Report sf-internal observations

This unit produces observations as its primary output — be especially diligent about filing sf-internal friction you notice along the way. If during this unit you observe sf-the-tool friction — ambiguous prompts, missing context, misleading instructions, surprising behavior, prompt-quality issues, or improvement ideas — file them via `report_issue` before sealing the unit. This is the only way these observations reach forge's backlog and get triaged. Over-reporting is preferred to under-reporting; dedup happens later. Do NOT use this to file bugs in the user's project; only sf-the-tool itself. Do NOT autonomously act on or fix existing backlog entries — your scope is your unit.
