Loading…
Workflow goal
Analyzes a collection of user stories to identify redundancies, overlaps, scoping issues, contradictions, and other quality problems. Produces an actionable report for story refinement.
Variable Source Value Phase Status
User Stories Folder
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-01_document_upload.md
Title: US-01_document_upload.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-02_document_metadata.md
Title: US-02_document_metadata.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-03_submit_for_review.md
Title: US-03_submit_for_review.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-04_approval_threshold.md
Title: US-04_approval_threshold.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-05_complete_review_workflow.md
Title: US-05_complete_review_workflow.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-06_reviewer_assignment.md
Title: US-06_reviewer_assignment.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-07_document_submission_process.md
Title: US-07_document_submission_process.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-08_review_deadline_handling.md
Title: US-08_review_deadline_handling.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-09_single_approval_low_priority.md
Title: US-09_single_approval_low_priority.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-10_comment_notification.md
Title: US-10_comment_notification.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-11_comment_read_receipt.md
Title: US-11_comment_read_receipt.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-12_deadline_extension_request.md
Title: US-12_deadline_extension_request.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-13_document_archive.md
Title: US-13_document_archive.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-14_review_statistics.md
Title: US-14_review_statistics.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_with_issues/US-15_system_integration.md
Title: US-15_system_integration.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
15 files

User Stories Folder

US-01_document_upload.md File: samples/user_stories_with_issues/US-01_document_upload.md • 479 Bytes
# US-01: Document Upload

**As a** document author  
**I want to** upload documents to the review system  
**So that** I can submit them for approval

## Acceptance Criteria

- AC-01: User can select files from local storage
- AC-02: Supported formats: PDF, DOCX, XLSX
- AC-03: Maximum file size: 50MB
- AC-04: Upload progress is displayed
- AC-05: Uploaded document appears in "My Documents" list

## Notes

*Issue: Missing error handling - no AC for upload failure scenarios*

US-02_document_metadata.md File: samples/user_stories_with_issues/US-02_document_metadata.md • 495 Bytes
# US-02: Document Metadata

**As a** document author  
**I want to** add metadata to my uploaded documents  
**So that** reviewers understand the context

## Acceptance Criteria

- AC-01: User can set document title (required, max 200 chars)
- AC-02: User can set document category (required, dropdown)
- AC-03: User can add description (optional, max 2000 chars)
- AC-04: User can set priority: Low, Medium, High, Critical
- AC-05: User can set review deadline (required, must be future date)

US-03_submit_for_review.md File: samples/user_stories_with_issues/US-03_submit_for_review.md • 544 Bytes
# US-03: Submit Document for Review

**As a** document author  
**I want to** submit my document for review  
**So that** the approval process can begin

## Acceptance Criteria

- AC-01: Submit button available for documents with complete metadata
- AC-02: System validates all required fields before submission
- AC-03: Document status changes to "Pending Review"
- AC-04: Author receives confirmation notification
- AC-05: Document becomes read-only after submission

## Notes

*Issue: Redundant with US-07 - both cover document submission*

US-04_approval_threshold.md File: samples/user_stories_with_issues/US-04_approval_threshold.md • 507 Bytes
# US-04: Approval Threshold

**As a** compliance officer  
**I want** documents to require approval from at least 2 reviewers  
**So that** we maintain quality standards

## Acceptance Criteria

- AC-01: Document needs minimum 2 approvals to be fully approved
- AC-02: System tracks approval count per document
- AC-03: Final approval triggers "Approved" status
- AC-04: Partial approval shows "X of 2 approvals received"

## Notes

*Issue: Contradicts US-09 which says low priority needs only 1 approval*

US-05_complete_review_workflow.md File: samples/user_stories_with_issues/US-05_complete_review_workflow.md • 1.0 kB
# US-05: Complete Review Workflow

**As a** reviewer  
**I want to** manage the entire document review process  
**So that** documents are properly evaluated

## Acceptance Criteria

- AC-01: Reviewer can view assigned documents in a queue
- AC-02: Reviewer can open documents for reading
- AC-03: Reviewer can add inline comments to documents
- AC-04: Reviewer can add general comments
- AC-05: Reviewer can request changes from author
- AC-06: Reviewer can approve document
- AC-07: Reviewer can reject document with reason
- AC-08: Reviewer can reassign document to another reviewer
- AC-09: Reviewer can set reminder for follow-up
- AC-10: Reviewer can view document history
- AC-11: Reviewer can compare document versions
- AC-12: Reviewer can export review summary
- AC-13: Reviewer can escalate to senior reviewer
- AC-14: System sends notification for each action

## Notes

*Issue: Scoping problem - this is an epic in disguise with 14 acceptance criteria covering multiple distinct features*

US-06_reviewer_assignment.md File: samples/user_stories_with_issues/US-06_reviewer_assignment.md • 560 Bytes
# US-06: Reviewer Assignment

**As a** team lead  
**I want to** assign reviewers to submitted documents  
**So that** appropriate experts review each document

## Acceptance Criteria

- AC-01: Team lead can view unassigned documents
- AC-02: Team lead can select reviewers from available pool
- AC-03: Team lead can assign multiple reviewers to one document
- AC-04: Assigned reviewers receive notification
- AC-05: Assignment timestamp is recorded

## Notes

*Issue: Missing edge case - what if the selected reviewer is unavailable (on leave, overloaded)?*

US-07_document_submission_process.md File: samples/user_stories_with_issues/US-07_document_submission_process.md • 484 Bytes
# US-07: Document Submission Process

**As a** user  
**I want to** send my document to the review queue  
**So that** it gets reviewed by the team

## Acceptance Criteria

- AC-01: User clicks "Send for Review" button
- AC-02: System checks metadata completeness
- AC-03: Document moves to review queue
- AC-04: User gets email confirmation
- AC-05: Document is locked for editing

## Notes

*Issue: Redundant with US-03 - nearly identical acceptance criteria for the same feature*

US-08_review_deadline_handling.md File: samples/user_stories_with_issues/US-08_review_deadline_handling.md • 566 Bytes
# US-08: Review Deadline Handling

**As a** compliance officer  
**I want** overdue reviews to be automatically escalated  
**So that** no document misses its deadline

## Acceptance Criteria

- AC-01: System checks deadlines daily at 00:00
- AC-02: Documents past deadline are marked "Overdue"
- AC-03: Overdue documents are escalated to department head
- AC-04: Email notification sent to all assigned reviewers
- AC-05: Escalation is logged in audit trail

## Notes

*Issue: Contradicts US-12 AC-04 which says NO escalation should occur during extension review*

US-09_single_approval_low_priority.md File: samples/user_stories_with_issues/US-09_single_approval_low_priority.md • 471 Bytes
# US-09: Single Approval for Low Priority

**As a** process owner  
**I want** low priority documents to need only 1 approval  
**So that** we can process simple documents faster

## Acceptance Criteria

- AC-01: Documents with priority "Low" need only 1 approval
- AC-02: Single approval changes status to "Approved"
- AC-03: Approval workflow is simplified for low priority items

## Notes

*Issue: Contradicts US-04 which says ALL documents need minimum 2 approvals*

US-10_comment_notification.md File: samples/user_stories_with_issues/US-10_comment_notification.md • 391 Bytes
# US-10: Comment Notification

**As a** document author  
**I want to** receive notifications when reviewers comment  
**So that** I can respond to feedback promptly

## Acceptance Criteria

- AC-01: Email sent when new comment is added
- AC-02: Email includes comment text and reviewer name
- AC-03: Email includes link to document
- AC-04: Notification can be configured in user settings

US-11_comment_read_receipt.md File: samples/user_stories_with_issues/US-11_comment_read_receipt.md • 364 Bytes
# US-11: Comment Read Receipt

**As a** reviewer  
**I want to** know when the author has read my comment  
**So that** I know they are aware of my feedback

## Acceptance Criteria

- AC-01: Read status is tracked per comment
- AC-02: Reviewer can see "Read" indicator

## Notes

*Issue: Scoping problem - too small, should be grouped with US-10 (notifications)*

US-12_deadline_extension_request.md File: samples/user_stories_with_issues/US-12_deadline_extension_request.md • 577 Bytes
# US-12: Deadline Extension Request

**As a** reviewer  
**I want to** request a deadline extension  
**So that** I have adequate time for complex reviews

## Acceptance Criteria

- AC-01: Reviewer can request extension with justification
- AC-02: Extension request goes to team lead for approval
- AC-03: Original deadline remains until extension approved
- AC-04: If deadline passes during extension review, NO escalation occurs
- AC-05: Team lead can approve or reject extension

## Notes

*Issue: AC-04 contradicts US-08 which says overdue documents are ALWAYS escalated*

US-13_document_archive.md File: samples/user_stories_with_issues/US-13_document_archive.md • 409 Bytes
# US-13: Document Archive

**As a** administrator  
**I want to** archive approved documents  
**So that** they are stored for compliance purposes

## Acceptance Criteria

- AC-01: Approved documents can be manually archived
- AC-02: Archived documents are moved to archive storage
- AC-03: Archive retains full document history
- AC-04: Archived documents are searchable
- AC-05: Retention period: 10 years

US-14_review_statistics.md File: samples/user_stories_with_issues/US-14_review_statistics.md • 408 Bytes
# US-14: Review Statistics

**As a** manager  
**I want to** view review statistics dashboard  
**So that** I can monitor team performance

## Acceptance Criteria

- AC-01: Dashboard shows documents reviewed this month
- AC-02: Dashboard shows average review time
- AC-03: Dashboard shows overdue document count
- AC-04: Dashboard shows reviewer workload distribution
- AC-05: Data can be exported to Excel

US-15_system_integration.md File: samples/user_stories_with_issues/US-15_system_integration.md • 532 Bytes
# US-15: System Integration

**As a** user  
**I want** the system to integrate with our other tools  
**So that** I don't have to switch between applications

## Acceptance Criteria

- AC-01: Documents can be imported from the system
- AC-02: Approved documents are synced to the system
- AC-03: User authentication uses the system SSO
- AC-04: Notifications appear in the system
- AC-05: Integration errors are logged

## Notes

*Issue: Unclear boundaries - "the system" is undefined. Which system? SharePoint? SAP? Salesforce?*

1 Redundancy Analysis
Identify redundant and duplicate user stories
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Analyze the provided user stories to identify redundancies and duplicates.

Output structure:

# Redundancy Analysis

## Full Duplicates

| Story A | Story B | Similarity | Recommendation |
|---------|---------|------------|----------------|
| US-XXX | US-YYY | 95% | Merge into US-XXX |

## Partial Overlaps

| Story A | Story B | Overlapping Aspect | Impact | Recommendation |
|---------|---------|-------------------|--------|----------------|
| US-XXX | US-YYY | [What overlaps] | High/Medium/Low | [Action] |

## Same Business Rule, Different Stories

| Business Rule | Stories | Recommendation |
|---------------|---------|----------------|
| [Rule description] | US-XXX, US-YYY, US-ZZZ | Consolidate into single story |

Guidelines:
- Compare each story against all others
- Identify semantic duplicates (same requirement, different wording)
- Note partial overlaps that could cause confusion
- Flag stories that address the same business rule
User Prompt (raw)
User Stories:
{userStoriesInput}

Identify all redundancies, duplicates, and overlaps.
2 Scoping Analysis
Identify scoping issues in user stories
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Analyze the provided user stories to identify scoping issues.

Output structure:

# Scoping Analysis

## Stories Too Large (Epics in Disguise)

| Story | Problem | Suggested Split |
|-------|---------|----------------|
| US-XXX | Contains 5+ acceptance criteria spanning multiple features | Split into: [list] |

## Stories Too Small (Should Be Grouped)

| Stories | Common Theme | Suggested Grouping |
|---------|--------------|-------------------|
| US-XXX, US-YYY | Both about same field validation | Combine into single validation story |

## Unclear Boundaries

| Story | Issue | Clarification Needed |
|-------|-------|---------------------|
| US-XXX | "System should..." but which system? | Specify target system |

## Missing Context

| Story | Missing Element | Impact |
|-------|-----------------|--------|
| US-XXX | No acceptance criteria | Cannot test or verify |

Guidelines:
- Flag stories with more than 5 acceptance criteria
- Identify stories that are really epics
- Find atomic stories that should be grouped
- Note missing boundary definitions
User Prompt (raw)
User Stories:
{userStoriesInput}

Identify all scoping issues.
3 Contradiction Analysis
Identify contradictions and conflicts between stories
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Analyze the provided user stories to identify contradictions and conflicts.

Output structure:

# Contradiction Analysis

## Direct Contradictions

| Story A | Story B | Contradiction | Severity | Resolution Needed |
|---------|---------|---------------|----------|-------------------|
| US-XXX | US-YYY | Story A says X must be required; Story B says X is optional | Critical | Stakeholder decision |

## Conflicting Behaviors

| Scenario | Story A Says | Story B Says | Impact |
|----------|--------------|--------------|--------|
| [When condition] | [Behavior A] | [Behavior B] | [What breaks] |

## Incompatible Data Requirements

| Data Element | Story A | Story B | Conflict |
|--------------|---------|---------|----------|
| [Field name] | Type: String | Type: Integer | Type mismatch |

## Timeline/Sequence Conflicts

| Process | Story A Sequence | Story B Sequence | Conflict |
|---------|------------------|------------------|----------|
| [Process name] | A → B → C | A → C → B | Order matters? |

Guidelines:
- Compare business rules across stories
- Check for conflicting validations
- Identify mutually exclusive requirements
- Flag race conditions or sequence conflicts
User Prompt (raw)
User Stories:
{userStoriesInput}

Identify all contradictions and conflicts.
4 Gap Analysis
Identify gaps and missing coverage
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Analyze the provided user stories to identify gaps and missing coverage.

Output structure:

# Gap Analysis

## Missing Error Handling

| Happy Path Story | Missing Error Scenario | Suggested Story |
|------------------|----------------------|----------------|
| US-XXX: Create record | What if creation fails? | Add error handling story |

## Missing Edge Cases

| Story | Covered Scenario | Missing Edge Case |
|-------|------------------|-------------------|
| US-XXX | Normal date input | Empty date, past date, future date limits |

## Incomplete User Journeys

| Journey | Covered Steps | Missing Steps |
|---------|---------------|---------------|
| [User journey name] | Step 1, 2, 4 | Step 3 (what happens between 2 and 4?) |

## Missing Actors

| Story | Current Actor | Potentially Missing Actor |
|-------|---------------|---------------------------|
| US-XXX | "As a user" | What about admin? What about system? |

## Integration Gaps

| Story | Internal Process | Missing Integration |
|-------|------------------|--------------------|
| US-XXX | Save data | No story for syncing to external system |

Guidelines:
- For each happy path, check for error handling
- Look for missing boundary conditions
- Trace user journeys for completeness
- Check all actor types are covered
User Prompt (raw)
User Stories:
{userStoriesInput}

Identify all gaps and missing coverage.
5 Verification Report
Consolidate all findings into prioritized action report
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Consolidate all analysis findings into a prioritized action report.

Output structure:

# User Stories Verification Report

## Executive Summary

- Total stories analyzed: X
- Critical issues: X
- High priority issues: X
- Medium priority issues: X
- Low priority issues: X

## Critical Issues (Must Fix Before Development)

| # | Issue Type | Stories Affected | Description | Recommended Action |
|---|------------|------------------|-------------|--------------------||
| 1 | Contradiction | US-XXX, US-YYY | [Summary] | [Action] |

## High Priority Issues (Should Fix Soon)

| # | Issue Type | Stories Affected | Description | Recommended Action |
|---|------------|------------------|-------------|--------------------|

## Medium Priority Issues (Fix When Possible)

| # | Issue Type | Stories Affected | Description | Recommended Action |
|---|------------|------------------|-------------|--------------------|

## Low Priority Issues (Nice to Have)

| # | Issue Type | Stories Affected | Description | Recommended Action |
|---|------------|------------------|-------------|--------------------|

## Story-by-Story Summary

| Story ID | Issues Found | Priority Actions |
|----------|--------------|------------------|
| US-XXX | 2 issues | Fix contradiction with US-YYY |

## Recommendations

1. [Top recommendation]
2. [Second recommendation]
3. [Third recommendation]

Guidelines:
- Prioritize contradictions as critical
- Group related issues
- Provide specific, actionable recommendations
- Include effort estimates where possible
User Prompt (raw)
User Stories:
{userStoriesInput}

Redundancy Analysis:
{redundancy_analysis}

Scoping Analysis:
{scoping_analysis}

Contradiction Analysis:
{contradiction_analysis}

Gap Analysis:
{gap_analysis}

Consolidate into a prioritized action report.