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/specs/conversational-registration/spec.md

@@ -0,0 +1,67 @@
+## ADDED Requirements
+
+### Requirement: Agent guides registration conversation
+The system SHALL provide an AI agent that engages parents in natural conversation to collect child registration information.
+
+#### Scenario: Parent initiates registration
+- **WHEN** a parent starts a conversation with intent to register
+- **THEN** the agent SHALL greet them and begin asking registration questions one at a time
+
+#### Scenario: Agent adapts to responses
+- **WHEN** a parent provides an answer that requires follow-up
+- **THEN** the agent SHALL ask relevant clarifying questions before moving to the next topic
+
+### Requirement: Agent collects required registration fields
+The system SHALL collect all required information for a complete registration: child's name, child's age/date of birth, parent/guardian contact information, desired booking days, and any special needs or requirements.
+
+#### Scenario: All required fields collected
+- **WHEN** the agent has gathered all required registration fields
+- **THEN** the agent SHALL confirm the collected information with the parent before submission
+
+#### Scenario: Missing required field
+- **WHEN** the parent attempts to complete registration with missing required fields
+- **THEN** the agent SHALL identify and request the missing information
+
+### Requirement: Agent handles special needs information
+The system SHALL ask about special needs only when relevant and collect detailed information when indicated.
+
+#### Scenario: Parent indicates special needs
+- **WHEN** a parent indicates their child has special needs or requirements
+- **THEN** the agent SHALL ask follow-up questions to understand the specific needs
+
+#### Scenario: No special needs indicated
+- **WHEN** a parent indicates no special needs
+- **THEN** the agent SHALL proceed without additional special needs questions
+
+### Requirement: Agent validates registration completeness
+The system SHALL validate that all required fields are present and properly formatted before finalizing a registration.
+
+#### Scenario: Valid registration data
+- **WHEN** all required fields are collected and valid
+- **THEN** the agent SHALL allow the registration to be submitted
+
+#### Scenario: Invalid data format
+- **WHEN** the parent provides data in an invalid format (e.g., invalid date, malformed email)
+- **THEN** the agent SHALL politely request the information again with guidance on the expected format
+
+### Requirement: Agent handles conversation interruptions
+The system SHALL maintain conversation state and allow parents to resume interrupted registrations.
+
+#### Scenario: Parent asks unrelated question mid-registration
+- **WHEN** a parent asks a question about fees or policies during registration
+- **THEN** the agent SHALL answer the question and offer to continue the registration
+
+#### Scenario: Conversation timeout
+- **WHEN** a registration conversation has been inactive for an extended period
+- **THEN** the system SHALL preserve collected data and allow resumption when the parent returns
+
+### Requirement: Agent supports conversation in natural language
+The system SHALL understand varied phrasings and respond naturally rather than requiring specific keywords or commands.
+
+#### Scenario: Varied input formats
+- **WHEN** a parent provides information in different formats (e.g., "my son is 4" vs "he's four years old" vs "DOB: 2021-03-15")
+- **THEN** the agent SHALL correctly interpret and extract the relevant information
+
+#### Scenario: Natural language responses
+- **WHEN** the agent responds to the parent
+- **THEN** responses SHALL be conversational, friendly, and appropriate for parent communication