What it solves
Large PRDs often contain multiple independent changes. Comet can split them into smaller OpenSpec changes so each has a clear proposal, design, build, verify, and archive path.
When splitting is triggered
Splitting is useful when the request contains unrelated domains, multiple user journeys, separate rollout risks, independently deliverable work, or scope that would make one design too broad.
Splitting flow
Comet identifies candidate changes, asks for your decision, and then creates bounded changes instead of one oversized workflow.
Your choices
You can usually choose to split now, keep one workflow, or defer part of the scope.
How to proceed after splitting
Work through changes one at a time unless you intentionally parallelize them. Archive completed changes before mixing unrelated work.
Split and presets
Hotfix and tweak work should stay small. If a preset expands into multi-change scope, upgrade to the full workflow and split deliberately.Last modified on July 1, 2026
