# user-story-splitting-prompt-template.md
## User Story Splitting Case Logic:
1. Does it contain multiple workflow steps? If yes, split the story along workflow steps.
2. Does it introduce business rule variations? If yes, split the story along business rule variations.
3. Does it demonstrate variations in data? If yes, split the story along with variations in data.
4. Does it possess complex acceptance criteria? If yes, split the story along discrete "when" actions or "then" outcomes.
5. Does it require a major effort to build? If yes, split the story along major effort milestones.
6. Does it incorporate external dependencies? If yes, split the story along external dependencies.
7. Does it take a significant DevOps effort? If yes, split the story along the key DevOps steps.
8. If none of the above criteria apply, consider using Tiny Acts of Discovery (TADs) to unpack unknowns, assumptions, and complexity and refine the story accordingly.
## User Story Format Prompt Template:
_The following format combines the Mike Cohn User Story Format augmented by a Gherkin-style acceptance criterion._
### User Story [User Story Number ID]:
- **Summary**: [brief, memorable, human-readable story title with how we're providing value to the persona]
#### Use Case:
- **As a** [user name if available, otherwise user persona, otherwise user role or title],
- **I want to** [action user takes to get to outcome],
- **so that** [desired outcome by the user].
#### Acceptance Criteria:
(_Note 1: Givens are pre-conditions, so don't feel limited to just 3 Givens._
_Note 2: There should only be one "When" and one "Then" statement that aligns with the use case's "I want to" action and "so that" outcome._
_Note 3: Multiple "whens" and "thens" are a good indicator a story must be split._)
- **Scenario**: [brief, human-readable user scenario with how we're providing value to the persona]
- **Given**: [Initial context or precondition]
- **and Given**: [additional context or preconditions based on the user's context]
- **and Given** [additional context or preconditions that support the 'Use Case' as needed]
- **and Given** [additional user interface-focused context or preconditions that ensure the 'When' event can happen]
- **and Given** [additional outcomes-focused context or preconditions that ensure the 'Then' outcome is delivered]
- **When**: [Event occurs that is connected to the use case action]
- **Then**: [Expected outcome that is connected to the user case outcome]
## AI Assitant Output Example
### Original User Story/Epic/Feature:
- [original user story, epic, or feature rendered using the User Story Format Prompt Template]
### Suggested Splits:
1. Split 1 using **[split logic rule used]**:
- [left side of the first user split version of the story, epic, or feature rendered using the User Story Format Prompt Template]
- [right side of the first user split version of the story, epic, or feature rendered using the User Story Format Prompt Template]
2. Split 2 using **[split logic rule used]**:
- [left side of the second user split version of the story, epic, or feature rendered using the User Story Format Prompt Template]
- [right side of the second user split version of the story, epic, or feature rendered using the User Story Format Prompt Template]
3. Split 3 using **[split logic rule used]**:
- [left side of the third user split version of the story, epic, or feature rendered using the User Story Format Prompt Template]
- [right side of the third user split version of the story, epic, or feature rendered using the User Story Format Prompt Template]
## End-User Product Manager Instruction:
Please provide the user story you would like to split:
---
*This prompt is adapted from [Product Manager Prompts](https://github.com/deanpeters/product-manager-prompts) by Dean Peters (MIT License).*