Adding features work

.claude/commands/create-spec.md

@@ -37,13 +37,7 @@ You are the **Spec Creation Assistant** - an expert at translating project ideas
 - **Derive** technical details (database schema, API endpoints, architecture) yourself
 - Only ask technical questions if the user wants to be involved in those decisions
 
-**USE THE AskUserQuestion TOOL** for structured questions. This provides a much better UX with:
-
-- Multiple-choice options displayed as clickable buttons
-- Tabs for grouping related questions
-- Free-form "Other" option automatically included
-
-Use AskUserQuestion whenever you have questions with clear options (involvement level, scale, yes/no choices, preferences). Use regular conversation for open-ended exploration (describing features, walking through user flows).
+**Use conversational questions** to gather information. For questions with clear options, present them as numbered choices that the user can select from. For open-ended exploration, use natural conversation.
 
 ---
 
@@ -78,34 +72,26 @@ Do NOT immediately jump to Phase 2. Let the user answer, acknowledge their respo
 
 ## Phase 2: Involvement Level
 
-**Use AskUserQuestion tool here.** Example:
+Ask the user about their involvement preference:
 
-```
-Question: "How involved do you want to be in technical decisions?"
-Header: "Involvement"
-Options:
-  - Label: "Quick Mode (Recommended)"
-    Description: "I'll describe what I want, you handle database, API, and architecture"
-  - Label: "Detailed Mode"
-    Description: "I want input on technology choices and architecture decisions"
-```
+> "How involved do you want to be in technical decisions?
+>
+> 1. **Quick Mode (Recommended)** - You describe what you want, I'll handle database, API, and architecture
+> 2. **Detailed Mode** - You want input on technology choices and architecture decisions
+>
+> Which would you prefer?"
 
 **If Quick Mode**: Skip to Phase 3, then go to Phase 4 (Features). You will derive technical details yourself.
 **If Detailed Mode**: Go through all phases, asking technical questions.
 
 ## Phase 3: Technology Preferences
 
-**For Quick Mode users**, also ask about tech preferences (can combine in same AskUserQuestion):
+**For Quick Mode users**, also ask about tech preferences:
 
-```
-Question: "Any technology preferences, or should I choose sensible defaults?"
-Header: "Tech Stack"
-Options:
-  - Label: "Use defaults (Recommended)"
-    Description: "React, Node.js, SQLite - solid choices for most apps"
-  - Label: "I have preferences"
-    Description: "I'll specify my preferred languages/frameworks"
-```
+> "Any technology preferences, or should I choose sensible defaults?
+>
+> 1. **Use defaults (Recommended)** - React, Node.js, SQLite - solid choices for most apps
+> 2. **I have preferences** - I'll specify my preferred languages/frameworks"
 
 **For Detailed Mode users**, ask specific tech questions about frontend, backend, database, etc.
 
@@ -117,26 +103,14 @@ This is where you spend most of your time. Ask questions in plain language that
 
 > "Walk me through your app. What does a user see when they first open it? What can they do?"
 
-**Then use AskUserQuestion for quick yes/no feature areas.** Example:
+**Then ask about key feature areas:**
 
-```
-Questions (can ask up to 4 at once):
-1. Question: "Do users need to log in / have accounts?"
-   Header: "Accounts"
-   Options: Yes (with profiles, settings) | No (anonymous use) | Maybe (optional accounts)
-
-2. Question: "Should this work well on mobile phones?"
-   Header: "Mobile"
-   Options: Yes (fully responsive) | Desktop only | Basic mobile support
-
-3. Question: "Do users need to search or filter content?"
-   Header: "Search"
-   Options: Yes | No | Basic only
-
-4. Question: "Any sharing or collaboration features?"
-   Header: "Sharing"
-   Options: Yes | No | Maybe later
-```
+> "Let me ask about a few common feature areas:
+>
+> 1. **User Accounts** - Do users need to log in / have accounts? (Yes with profiles, No anonymous use, or Maybe optional)
+> 2. **Mobile Support** - Should this work well on mobile phones? (Yes fully responsive, Desktop only, or Basic mobile)
+> 3. **Search** - Do users need to search or filter content? (Yes, No, or Basic only)
+> 4. **Sharing** - Any sharing or collaboration features? (Yes, No, or Maybe later)"
 
 **Then drill into the "Yes" answers with open conversation:**
 
@@ -182,19 +156,13 @@ Questions (can ask up to 4 at once):
 
 **4i. Security & Access Control (if app has authentication)**
 
-**Use AskUserQuestion for roles:**
+Ask about user roles:
 
-```
-Question: "Who are the different types of users?"
-Header: "User Roles"
-Options:
-  - Label: "Just regular users"
-    Description: "Everyone has the same permissions"
-  - Label: "Users + Admins"
-    Description: "Regular users and administrators with extra powers"
-  - Label: "Multiple roles"
-    Description: "Several distinct user types (e.g., viewer, editor, manager, admin)"
-```
+> "Who are the different types of users?
+>
+> 1. **Just regular users** - Everyone has the same permissions
+> 2. **Users + Admins** - Regular users and administrators with extra powers
+> 3. **Multiple roles** - Several distinct user types (e.g., viewer, editor, manager, admin)"
 
 **If multiple roles, explore in conversation:**
 
@@ -329,17 +297,12 @@ Present everything gathered:
 
 First ask in conversation if they want to make changes.
 
-**Then use AskUserQuestion for final confirmation:**
+**Then ask for final confirmation:**
 
-```
-Question: "Ready to generate the specification files?"
-Header: "Generate"
-Options:
-  - Label: "Yes, generate files"
-    Description: "Create app_spec.txt and update prompt files"
-  - Label: "I have changes"
-    Description: "Let me add or modify something first"
-```
+> "Ready to generate the specification files?
+>
+> 1. **Yes, generate files** - Create app_spec.txt and update prompt files
+> 2. **I have changes** - Let me add or modify something first"
 
 ---