feat: scaffold holiday booking project

01-intake-and-scope.md

@@ -0,0 +1,69 @@
+# 01. Intake and Scope
+
+## Purpose
+
+Define the project boundary, MVP target, and the decisions needed before design or implementation starts.
+
+## Scope
+
+- Confirm the project is a responsive holiday property booking website for one business with multiple properties.
+- Confirm the MVP includes:
+  - public browsing
+  - property detail pages
+  - availability search
+  - booking flow
+  - Stripe Checkout
+  - confirmation/failure handling
+  - booking/admin management
+  - editable content
+  - email notifications
+  - basic SEO
+- Record anything explicitly out of scope.
+- Lock the approved technical direction for planning:
+  - Next.js + TypeScript
+  - Bootstrap 5 + SCSS
+  - Next.js server routes/API layer for the MVP backend
+  - PostgreSQL
+  - Prisma
+  - session-based admin auth
+  - Stripe Checkout + webhooks
+  - transactional email provider abstraction
+  - S3-compatible image storage
+  - Docker-based dev/qa/prod environments
+
+## What Needs to Be Done
+
+- Extract the key business goals from the spec.
+- List the product areas that need separate planning.
+- Identify unresolved questions and assumptions.
+- Establish the delivery phase order.
+- Set the approval gate for the next document.
+
+## Proposed Phase Order
+
+1. Intake and scope
+2. Content architecture and data model
+3. Public website and search
+4. Booking, availability, and pricing
+5. Payments and notifications
+6. Admin console
+7. SEO, accessibility, and performance
+8. Implementation plan and launch readiness
+
+## Acceptance Criteria
+
+- The MVP scope is written in one place.
+- The non-MVP items are clearly marked.
+- Open questions are listed, not hidden inside later docs.
+- The approved stack is recorded for the project.
+- The phase order is explicit and reviewable.
+- The next planning step is obvious and sequenced.
+
+## Dependencies
+
+- Functional specification review.
+- Agreement on what counts as MVP.
+
+## Notes
+
+- This document is the start of the project plan, not a build task.