Ask the six optional setup questions after size so each tick can change suggested cards, keeping the answers on the draft and off the published Rule.

docs/create-flow.md

@@ -6,11 +6,11 @@ Product/engineering reference for the **custom** “Create rule” experience: U
 
 ## Product stages (Figma)
 
-The Figma **Create Community** sequence is the **source of truth** for the first segment of the wizard (eight frames). After **`review`**, the flow continues with **Create Custom CommunityRule** and **Review and complete** stages. The shipped URL sequence in [`FLOW_STEP_ORDER`](../app/(app)/create/utils/flowSteps.ts) **follows that trajectory**; stages are a **product** slice of that linear order, not separate routers today.
+The Figma **Create Community** sequence is the **source of truth** for the first segment of the wizard. After **`review`**, the flow continues with **Create Custom CommunityRule** and **Review and complete** stages. The shipped URL sequence in [`FLOW_STEP_ORDER`](../app/(app)/create/utils/flowSteps.ts) **follows that trajectory**; stages are a **product** slice of that linear order, not separate routers today.
 
 | Stage (Figma) | Purpose (summary) | `CreateFlowStep` values (in order) |
 | --- | --- | --- |
-| **Create Community** | Intro, naming, structure, context, size, upload, save progress (email), then community review. | `informational` → `community-name` → `community-structure` → `community-context` → `community-size` → `community-upload` → `community-save` → `review` |
+| **Create Community** | Intro, naming, structure, context, size, optional setup questions, upload, save progress (email), then community review. | `informational` → `community-name` → `community-structure` → `community-context` → `community-size` → `setup-questions` → `community-upload` → `community-save` → `review` |
 | **Create Custom CommunityRule** | Author the CommunityRule content and structure (core values + four card-stack categories). | `core-values` → `communication-methods` → `membership-methods` → `decision-approaches` → `conflict-management` |
 | **Review and complete** | Stakeholders, final card, publish, success. | `confirm-stakeholders` → `final-review` → `completed` |
 
@@ -31,17 +31,18 @@ Order is defined in code by [`FLOW_STEP_ORDER`](../app/(app)/create/utils/flowSt
 | 3 | Create Community | `community-structure` | `/create/community-structure` |
 | 4 | Create Community | `community-context` | `/create/community-context` |
 | 5 | Create Community | `community-size` | `/create/community-size` |
-| 6 | Create Community | `community-upload` | `/create/community-upload` |
-| 7 | Create Community | `community-save` | `/create/community-save` |
-| 8 | Create Community (review frame) | `review` | `/create/review` |
-| 9 | Create Custom CommunityRule | `core-values` | `/create/core-values` |
-| 10 | Create Custom CommunityRule | `communication-methods` | `/create/communication-methods` |
-| 11 | Create Custom CommunityRule | `membership-methods` | `/create/membership-methods` |
-| 12 | Create Custom CommunityRule | `decision-approaches` | `/create/decision-approaches` |
-| 13 | Create Custom CommunityRule | `conflict-management` | `/create/conflict-management` |
-| 14 | Review and complete | `confirm-stakeholders` | `/create/confirm-stakeholders` |
-| 15 | Review and complete | `final-review` | `/create/final-review` |
-| 16 | Review and complete | `completed` | `/create/completed` |
+| 6 | Create Community | `setup-questions` | `/create/setup-questions` |
+| 7 | Create Community | `community-upload` | `/create/community-upload` |
+| 8 | Create Community | `community-save` | `/create/community-save` |
+| 9 | Create Community (review frame) | `review` | `/create/review` |
+| 10 | Create Custom CommunityRule | `core-values` | `/create/core-values` |
+| 11 | Create Custom CommunityRule | `communication-methods` | `/create/communication-methods` |
+| 12 | Create Custom CommunityRule | `membership-methods` | `/create/membership-methods` |
+| 13 | Create Custom CommunityRule | `decision-approaches` | `/create/decision-approaches` |
+| 14 | Create Custom CommunityRule | `conflict-management` | `/create/conflict-management` |
+| 15 | Review and complete | `confirm-stakeholders` | `/create/confirm-stakeholders` |
+| 16 | Review and complete | `final-review` | `/create/final-review` |
+| 17 | Review and complete | `completed` | `/create/completed` |
 
 **Primary entry:** marketing header **Create rule** and profile **Create new custom Rule** both run **`prepareFreshCreateFlowEntry`** then navigate to **`/create`**, which redirects to **`/create/informational`** (see [`Top.container.tsx`](../app/components/navigation/Top/Top.container.tsx) and [`ProfilePageClient.tsx`](../app/(app)/profile/ProfilePageClient.tsx)).
 
@@ -87,7 +88,7 @@ From that page, **Customize** pre-fills the custom-rule selections on the curren
 **Entering a template before community stage is done.** Both handlers apply their side effects eagerly (prefill for Customize; `sections` for Use without changes) *and* pin a `pendingTemplateAction: { slug, mode }` when the community questionnaire still needs to run.
 
 - **Customize** routes to `/create/informational` and walks the full Create Community questionnaire. Once the user reaches `/create/review`, [`CommunityReviewScreen`](../app/(app)/create/screens/review/CommunityReviewScreen.tsx) reads the action on mount, clears it via `updateState`, and `router.replace`s to `/create/core-values`. `replace` (not `push`) keeps `community-save` as the Back-button target from that destination.
-- **Use without changes (direct from a template)** — home Popular templates, `/templates` without `fromFlow`, or a pasted review-template URL. Always routes to `/create/community-name` and walks **name → description → optional photo**, then `/create/confirm-stakeholders`. A leftover draft title is **not** “community already done”; those identity fields are cleared so cache cannot skip or pre-fill the path. Intro, structure, size, save, community review, and custom-rule authoring are skipped. Back from name returns to template review.
+- **Use without changes (direct from a template)** — home Popular templates, `/templates` without `fromFlow`, or a pasted review-template URL. Always routes to `/create/community-name` and walks **name → description → optional photo**, then `/create/confirm-stakeholders`. A leftover draft title is **not** “community already done”; those identity fields are cleared so cache cannot skip or pre-fill the path. Intro, structure, size, setup questions, save, community review, and custom-rule authoring are skipped. Back from name returns to template review.
 - **Use without changes (in-flow)** — `/create/review` → `/create/templates` → template. Community identity is already collected, so this action seeds the template and routes to `/create/confirm-stakeholders`. Back returns to template review.
 
 The action for Customize is cleared on the first fire so later direct visits to `/create/review` render normally. The review screen is not part of the Use-without-changes identity path. If they land on `/create/review` with a leftover Use-without-changes pin, the screen `replace`s to `community-name`.