[Change] Story complexity and splitting hints support #171
Description
Why
The backlog-refinement spec includes "Story Complexity Analysis" and related scenarios (complexity score, multi-sprint detection, splitting suggestion), but this behavior is not implemented. Teams need complexity scores, flagging of stories > 13 points for potential splitting, and splitting suggestions in refinement output. Without this, refinement sessions do not surface size/scope risks.
What Changes
- Implement complexity calculation (story_points, business_value) and configurable threshold for "needs splitting" flag.
- Add splitting detection with suggested split points and rationale.
- Integrate into
specfact backlog refine: include "Story splitting suggestion" block for complex stories. - E3 (plan): Splitting suggestions consider dependency edges (minimize cross-team coupling) and "blast radius" signals. Provide patch output: "split proposal" as suggested child stories with titles + AC + links. Acceptance: Splitting recommendation includes "dependency impact" section.
Acceptance Criteria
- Complexity score and needs_splitting predicate; splitting suggestion in refinement output.
- Splitting recommendation includes "dependency impact" section when dependency analysis available.
- Documentation updated for complexity and splitting hints.
OpenSpec Change Proposal: story-complexity-splitting-hints-support