Add project scope documentation for AI playgroup registration system

Define complete non-technical scope for replacing Google Forms registration
with an AI-powered conversational agent. Includes:

- Registration data requirements (13 fields with validation rules)
- Knowledge base content (fees, regulations, schedule, FAQ from official PDFs)
- Conversation flow design with bilingual support (German/English)
- Agent personality guidelines (warm & friendly tone)
- Admin notification routing by playgroup type
- Email reminder system for incomplete registrations
- Data export formats (CSV/JSON)
- Channel configuration (email + chat)
- Release priorities (MVP scope defined)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

openspec/changes/define-project-scope/tasks.md

@@ -0,0 +1,47 @@
+## 1. Define Registration Data Requirements
+
+- [x] 1.1 Document all required registration fields (child name, DOB/age, parent contact, booking days, special needs)
+- [x] 1.2 Document optional registration fields and when to collect them
+- [x] 1.3 Define validation rules for each field (formats, constraints, allowed values)
+- [x] 1.4 Create registration data schema (JSON schema or equivalent)
+
+## 2. Prepare Knowledge Base Content
+
+- [x] 2.1 Compile current service fee information (rates, payment terms, discounts)
+- [x] 2.2 Document playgroup regulations and policies
+- [x] 2.3 Document opening hours and booking availability
+- [x] 2.4 Compile frequently asked questions and answers
+- [x] 2.5 Organize knowledge base content into structured markdown files
+
+## 3. Define Conversation Flows
+
+- [x] 3.1 Map out the registration conversation flow (question sequence, branches)
+- [x] 3.2 Define agent personality and tone guidelines
+- [x] 3.3 Write sample agent responses for common scenarios
+- [x] 3.4 Define how agent handles mixed intent (registration + questions)
+- [x] 3.5 Define conversation timeout and resumption behavior
+
+## 4. Define Notification Requirements
+
+- [x] 4.1 Design notification email template content
+- [x] 4.2 Define which registration fields appear in notification summary
+- [x] 4.3 Specify admin notification email address(es)
+
+## 5. Define Data Export Requirements
+
+- [x] 5.1 Define required export formats (CSV columns, JSON structure)
+- [x] 5.2 Document how exports integrate with existing admin workflow
+- [x] 5.3 Define any filtering or query requirements for exports
+
+## 6. Channel-Specific Requirements
+
+- [x] 6.1 Define email address for registration channel
+- [x] 6.2 Define chat interface branding requirements (logo, colors, welcome message)
+- [x] 6.3 Document any channel-specific behavior differences
+
+## 7. Review and Finalize Scope
+
+- [x] 7.1 Review all documented requirements with stakeholders
+- [x] 7.2 Identify any gaps or missing requirements
+- [x] 7.3 Prioritize features for initial release vs. future iterations
+- [x] 7.4 Finalize and approve project scope documentation