# Task Split Assessment

Open Orchestra treats oversized work as an advisory delivery risk before
implementation starts. The goal is not to block small tasks; it is to make PO/BA
and Architect reviews explicit when one backlog item is trying to carry multiple
stories or too much technical coupling.

## Ownership

- Product Owner / BA review functional oversize: multiple journeys, unrelated
  outcomes, too many acceptance criteria, hidden support/release scope, or UX
  discovery that expands the story.
- Architect reviews technical complexity: too many modules, boundaries,
  integrations, data changes, runtime changes, UI changes, infra changes, or
  release surfaces in one task.

## Expected Output

When split risk is found, the reviewer records a recommendation with:

- rationale
- proposed child stories or technical slices
- dependency order
- risks
- owner roles

Routine small fixes stay as one task when they do not exceed the advisory
thresholds.

## CLI Surface

`orchestra workflow phase-plan --task <id> --json` includes
`splitAssessment`. The field is advisory and can be attached to a review,
clarification, decision, or follow-up task.