design-split-options

Generate 2-3 materially different decomposition options and compare them on ownership clarity, coupling, validation fit, sequencing, and hidden shared context risk. Write the comparison as candidate final task graphs in SPLIT_OPTIONS.md with one explicit recommendation.

Use split option comparison when task boundaries or sequencing are still ambiguous and committing directly to a task graph would lock in a weak decomposition. If the split is already obvious, proceed directly to authoring the task graph.

Evaluate options on ownership clarity, coupling between tasks, validation fit, sequencing and uncertainty reduction, risk of hidden shared context, and how easily each child task can be handed to a fresh agent.

You need the initiative's BRIEF.md, UBIQUITOUS_LANGUAGE.md, DECISIONS.md, INVARIANTS.md, REPO_MAP.md, CONTRACTS.md, and OPEN_QUESTIONS.md, plus the initiative packet and workflow contract references. The initiative should enter split_drafting status first.

Common mistakes include producing cosmetic variants of the same split, deferring the recommendation when evidence already favors one option, and writing changelog commentary about prior attempts instead of candidate final task graphs.