Loading…
Workflow goal
Transforms a collection of user stories into consolidated system documentation. Extracts and organizes business rules, processes, and data definitions from user stories into readable documentation.
Variable Source Value Phase Status
User Stories Folder
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/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_clean/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_clean/US-03_document_submission.md
Title: US-03_document_submission.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-04_approval_rules.md
Title: US-04_approval_rules.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-05_reviewer_assignment.md
Title: US-05_reviewer_assignment.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-06_document_review.md
Title: US-06_document_review.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-07_author_feedback_response.md
Title: US-07_author_feedback_response.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-08_deadline_management.md
Title: US-08_deadline_management.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-09_deadline_extension.md
Title: US-09_deadline_extension.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-10_comment_notifications.md
Title: US-10_comment_notifications.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-11_version_control.md
Title: US-11_version_control.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-12_approval_completion.md
Title: US-12_approval_completion.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/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_clean/US-14_statistics_dashboard.md
Title: US-14_statistics_dashboard.md
Updated:
Phase 2: Raw Content
⏳ Pending
Phase 3: Final Content
⏳ Pending
Phase 1: Metadata
✓ Ready
File:
ID: samples/user_stories_clean/US-15_sharepoint_integration.md
Title: US-15_sharepoint_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_clean/US-01_document_upload.md • 643 Bytes
# US-01: Document Upload with Error Handling

**As a** document author  
**I want to** upload documents to the Review Portal  
**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 with percentage
- AC-05: Uploaded document appears in "My Documents" list
- AC-06: If upload fails due to network error, user sees retry option
- AC-07: If file format is unsupported, user sees clear error message
- AC-08: If file exceeds size limit, user sees maximum allowed size

US-02_document_metadata.md File: samples/user_stories_clean/US-02_document_metadata.md • 619 Bytes
# US-02: Document Metadata Entry

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

## Acceptance Criteria

- AC-01: User can set document title (required, max 200 chars)
- AC-02: User can select document category from predefined list (required)
- 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 at least 3 business days in future)
- AC-06: Validation errors displayed inline next to affected fields

US-03_document_submission.md File: samples/user_stories_clean/US-03_document_submission.md • 575 Bytes
# US-03: Document Submission 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 enabled only when all required metadata is complete
- AC-02: System validates all required fields before submission
- AC-03: Document status changes from "Draft" to "Pending Assignment"
- AC-04: Author receives email confirmation with submission ID
- AC-05: Document becomes read-only after submission
- AC-06: Author can withdraw submission before reviewer assignment

US-04_approval_rules.md File: samples/user_stories_clean/US-04_approval_rules.md • 618 Bytes
# US-04: Priority-Based Approval Rules

**As a** compliance officer  
**I want** approval requirements to vary by document priority  
**So that** we balance thoroughness with efficiency

## Acceptance Criteria

- AC-01: Low priority documents require 1 approval
- AC-02: Medium priority documents require 2 approvals
- AC-03: High priority documents require 2 approvals + team lead sign-off
- AC-04: Critical priority documents require 3 approvals + compliance officer sign-off
- AC-05: Approval rules are displayed on document detail page
- AC-06: System enforces rules automatically and prevents premature approval

US-05_reviewer_assignment.md File: samples/user_stories_clean/US-05_reviewer_assignment.md • 693 Bytes
# US-05: 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 sees list of unassigned documents sorted by deadline
- AC-02: Team lead can view available reviewers and their current workload
- AC-03: Team lead can assign 1-3 reviewers per document based on priority rules
- AC-04: Assigned reviewers receive email notification with deadline
- AC-05: Assignment timestamp and assigner recorded in audit log
- AC-06: If selected reviewer is on leave, system shows warning with return date
- AC-07: Team lead can reassign if reviewer becomes unavailable

US-06_document_review.md File: samples/user_stories_clean/US-06_document_review.md • 645 Bytes
# US-06: Document Review Actions

**As a** reviewer  
**I want to** review assigned documents and provide feedback  
**So that** documents meet quality standards before approval

## Acceptance Criteria

- AC-01: Reviewer sees assigned documents in personal queue with deadlines
- AC-02: Reviewer can open document in built-in viewer
- AC-03: Reviewer can add inline comments on specific sections
- AC-04: Reviewer can add general comments visible to all stakeholders
- AC-05: Reviewer can approve, reject, or request changes
- AC-06: Rejection requires mandatory reason (min 50 chars)
- AC-07: Request for changes requires at least one comment

US-07_author_feedback_response.md File: samples/user_stories_clean/US-07_author_feedback_response.md • 561 Bytes
# US-07: Author Response to Feedback

**As a** document author  
**I want to** respond to reviewer feedback  
**So that** I can address concerns and get approval

## Acceptance Criteria

- AC-01: Author notified by email when feedback is received
- AC-02: Author can view all comments in consolidated view
- AC-03: Author can reply to individual comments
- AC-04: Author can upload revised document version
- AC-05: Author can mark comments as "Addressed" or "Will not fix" with explanation
- AC-06: Reviewers notified when author responds or uploads revision

US-08_deadline_management.md File: samples/user_stories_clean/US-08_deadline_management.md • 625 Bytes
# US-08: Review Deadline Management

**As a** compliance officer  
**I want** deadline handling to be consistent and auditable  
**So that** we maintain compliance with review timelines

## Acceptance Criteria

- AC-01: System checks deadlines daily at 06:00 UTC
- AC-02: Documents 2 days before deadline: warning email to reviewers
- AC-03: Documents 1 day before deadline: escalation email to team lead
- AC-04: Documents past deadline: marked "Overdue" and escalated to department head
- AC-05: Pending extension requests pause escalation until decision
- AC-06: All deadline events logged in audit trail with timestamps

US-09_deadline_extension.md File: samples/user_stories_clean/US-09_deadline_extension.md • 669 Bytes
# US-09: Deadline Extension Request

**As a** reviewer  
**I want to** request a deadline extension for complex documents  
**So that** I can provide thorough feedback without rushing

## Acceptance Criteria

- AC-01: Reviewer can request extension with justification (min 100 chars)
- AC-02: Reviewer must specify requested new deadline
- AC-03: Extension request sent to team lead for approval
- AC-04: Team lead can approve, reject, or suggest alternative deadline
- AC-05: Original deadline remains until extension is explicitly approved
- AC-06: Maximum extension: 10 business days beyond original deadline
- AC-07: Extension history visible on document timeline

US-10_comment_notifications.md File: samples/user_stories_clean/US-10_comment_notifications.md • 602 Bytes
# US-10: Comment Notifications and Tracking

**As a** document stakeholder (author or reviewer)  
**I want to** track comment activity  
**So that** I stay informed about document discussions

## Acceptance Criteria

- AC-01: Email notification sent when new comment is added
- AC-02: Email includes comment text, author name, and document link
- AC-03: Read status tracked per comment per user
- AC-04: Comment author can see who has read their comment
- AC-05: Users can configure notification preferences (immediate, daily digest, off)
- AC-06: Unread comment count shown on document in queue view

US-11_version_control.md File: samples/user_stories_clean/US-11_version_control.md • 538 Bytes
# US-11: Document Version Control

**As a** document author  
**I want to** manage document versions  
**So that** reviewers can track changes between iterations

## Acceptance Criteria

- AC-01: Each upload creates a new version (v1, v2, v3, etc.)
- AC-02: All versions retained and accessible
- AC-03: Users can view side-by-side comparison of any two versions
- AC-04: Version history shows upload date, uploader, and file size
- AC-05: Latest version clearly marked as "Current"
- AC-06: Reviewers notified when new version uploaded

US-12_approval_completion.md File: samples/user_stories_clean/US-12_approval_completion.md • 543 Bytes
# US-12: Document Approval Completion

**As a** system  
**I want to** finalize approved documents  
**So that** they are properly recorded and distributed

## Acceptance Criteria

- AC-01: When approval threshold met, status changes to "Approved"
- AC-02: Approval timestamp and final approver recorded
- AC-03: Author receives email notification of approval
- AC-04: Approved document automatically queued for archival
- AC-05: Approval certificate generated with all reviewer signatures
- AC-06: Document locked from further modifications

US-13_document_archive.md File: samples/user_stories_clean/US-13_document_archive.md • 601 Bytes
# US-13: Document Archive

**As a** administrator  
**I want to** archive approved documents to the Compliance Archive System  
**So that** they are stored for regulatory compliance

## Acceptance Criteria

- AC-01: Approved documents archived within 24 hours of approval
- AC-02: Archive includes: document file, all versions, comments, audit trail
- AC-03: Archive stored in Compliance Archive System with unique reference ID
- AC-04: Archived documents searchable by ID, title, date, category
- AC-05: Retention period: 10 years from approval date
- AC-06: Archive integrity verified via checksum

US-14_statistics_dashboard.md File: samples/user_stories_clean/US-14_statistics_dashboard.md • 570 Bytes
# US-14: Review Statistics Dashboard

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

## Acceptance Criteria

- AC-01: Dashboard shows documents reviewed this month vs last month
- AC-02: Dashboard shows average review time by priority level
- AC-03: Dashboard shows overdue document count with drill-down
- AC-04: Dashboard shows reviewer workload distribution chart
- AC-05: Date range filter: last 7 days, 30 days, 90 days, custom
- AC-06: Data exportable to Excel format

US-15_sharepoint_integration.md File: samples/user_stories_clean/US-15_sharepoint_integration.md • 609 Bytes
# US-15: SharePoint Integration

**As a** user  
**I want** the Review Portal to integrate with SharePoint  
**So that** I can work seamlessly across systems

## Acceptance Criteria

- AC-01: Users can import documents directly from SharePoint document libraries
- AC-02: Approved documents sync to designated SharePoint archive folder
- AC-03: User authentication via Azure AD SSO (same credentials as SharePoint)
- AC-04: Review notifications appear in SharePoint notification panel
- AC-05: Integration errors logged with error code and retry option
- AC-06: Integration status shown on user profile page

1 Extracted Business Rules
Extract business rules and constraints from user stories
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Extract all business rules, constraints, and validations from the provided user stories.

Output structure:

# Business Rules

## [Category/Module Name]

| Rule ID | Rule Description | Source Story | Conditions | Expected Behavior |
|---------|-----------------|--------------|------------|-------------------|
| BR-001 | ... | US-XXX | When... | Then... |

Guidelines:
- Group rules by functional area or module
- Each rule should be atomic and testable
- Include the source user story reference
- Use When/Then format for conditions and behavior
- Flag any conflicting rules between stories
User Prompt (raw)
User Stories:
{userStoriesInput}

Extract all business rules from these user stories.
2 Extracted Data Model
Extract data elements and relationships from user stories
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Extract all data elements, fields, and their relationships from the provided user stories.

Output structure:

# Data Model

## Entities

| Entity | Description | Key Fields | Source Stories |
|--------|-------------|------------|----------------|

## Fields

| Field Name | Entity | Type | Valid Values | Constraints | Source |
|------------|--------|------|--------------|-------------|--------|

## Relationships

| Entity A | Relationship | Entity B | Cardinality | Source |
|----------|--------------|----------|-------------|--------|

Guidelines:
- Identify all data entities mentioned
- Document field types, valid values, and constraints
- Map relationships between entities
- Note any data transformations or mappings
User Prompt (raw)
User Stories:
{userStoriesInput}

Extract all data elements and relationships from these user stories.
3 Extracted Process Flows
Extract process flows and workflows from user stories
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Extract all process flows, workflows, and sequences from the provided user stories.

Output structure:

# Process Flows

## [Process Name]

**Trigger:** [What initiates this process]
**Actor:** [Who/what performs this process]
**Source:** [User story references]

### Steps

1. [Step description]
   - Input: [Required input]
   - Output: [Expected output]
   - Conditions: [If applicable]

### Decision Points

| Decision | Condition | Path A | Path B |
|----------|-----------|--------|--------|

### Integration Points

| Step | External System | Data Exchanged |
|------|-----------------|----------------|

Guidelines:
- Identify start and end points
- Document decision branches
- Note parallel processes if any
- Highlight integration touchpoints
User Prompt (raw)
User Stories:
{userStoriesInput}

Extract all process flows from these user stories.
4 Consolidated Documentation
Consolidate all extractions into unified documentation
pending
Value will be available once processing is complete.
Input will be available once processing is complete.
System Prompt (raw)
Consolidate the extracted information into a unified system documentation.

Output structure:

# System Documentation

## Overview

[Brief summary of what this documentation covers based on the user stories]

## 1. Business Rules

[Organized business rules from extraction, deduplicated and categorized]

## 2. Data Model

[Data entities, fields, and relationships from extraction]

## 3. Process Flows

[Process descriptions from extraction]

## 4. Integration Points

[Summary of external system interactions]

## 5. Open Questions

[Any ambiguities or missing information identified]

## Appendix: User Story Traceability

| User Story | Documented In |
|------------|---------------|
| US-XXX | Sections 1.2, 3.1 |

Guidelines:
- Remove duplicates across sections
- Resolve any contradictions (note if unresolvable)
- Ensure traceability back to source stories
- Flag gaps or incomplete information
User Prompt (raw)
User Stories:
{userStoriesInput}

Business Rules:
{business_rules}

Data Model:
{data_model}

Process Flows:
{process_flows}

Consolidate into unified documentation.