Service Legal Docs — Service Legal Document Set Generation Pipeline

Workflow

Phase 1: Preparation (Orchestrator performs directly)

1. Extract from user input:
   • Service Name: Company/service name
   • Service Type: SaaS, e-commerce, content platform, community, etc.
   • Service Region: Domestic, global (including EU or not)
   • Payment: Paid/free/freemium (in-app purchases, subscriptions)
   • Personal Data Collected (optional): List of data collected
   • Existing Materials (optional): Current terms, privacy policy, etc.
2. Create _workspace/ directory in the project root
3. Organize input and save to _workspace/00_input.md
4. Determine execution mode based on request scope

Phase 2: Team Formation and Execution

Tasks 1a, 1b, and 1c are executed in parallel. All three agents can work independently. However, agents communicate with each other during work to ensure cross-document alignment.

Inter-team Communication Flow:

• tos-specialist ↔ privacy-specialist: Coordinate privacy-related terms clauses
• tos-specialist ↔ consumer-analyst: Coordinate refund, cancellation, and copyright clauses
• privacy-specialist ↔ consumer-analyst: Coordinate personal data processing during payment and refund
• consistency-reviewer cross-validates all outputs. If 🔴 critical issues are found, revision requests are sent to the relevant agent (maximum 2 times)

Phase 3: Integration and Final Output

1. Verify all files in _workspace/
2. Confirm all 🔴 critical issues from the review report have been addressed
3. Report final summary to the user:
   • Terms of Service — 01_terms_of_service.md
   • Privacy Policy — 02_privacy_policy.md
   • Cookie Policy — 03_cookie_policy.md
   • Refund Policy — 04_refund_policy.md
   • Copyright Notice — 05_copyright_notice.md
   • Review Report — 06_review_report.md

Mode by Request Scope

Using Existing Files: If the user provides existing terms, privacy policy, etc., copy the relevant files to the appropriate numbered location in _workspace/ and skip the corresponding agent.

Data Transfer Protocol

Filename convention: {sequence}_{document_type}.{extension}

Error Handling

Test Scenarios

Normal Flow

Prompt: "I'm preparing to launch a SaaS service and need the full legal document set. The service is called TaskFlow, it's a monthly subscription model, and we collect email, name, and phone number at signup." Expected Result:

• Terms of Service: SaaS-specific clauses (subscription, service level, data ownership, etc.)
• Privacy Policy: Reflects email/name/phone number collection items
• Cookie Policy: Cookie type classification based on web service standards
• Refund Policy: Subscription model-specific withdrawal criteria
• Copyright Notice: SaaS content copyright provisions
• Review: Cross-document consistency verified across all 6 documents

Partial Flow

Prompt: "I already have the terms of service, just write the privacy policy" Expected Result:

• Switches to Privacy Policy Mode (privacy-specialist + reviewer)
• References existing terms for consistency verification

Error Flow

Prompt: "Create service terms, it's an app but I'll give you the details later" Expected Result:

• Full pipeline executes based on general mobile app standards
• All documents include "[Verification Required]" markers for items requiring service customization
• Review report includes "Document update required after confirming service details"

Agent Extended Skills