Based on the the requirements in .claude/requirements.md, and the technical specification in .claude/techspec.md, create a comprehensive task list organized by major feature areas (threads).

CRITICAL: Each task must be a DETAILED DESCRIPTION (2-4 sentences) that provides solid context for implementation!

TASK DESCRIPTION MUST INCLUDE:
1. WHERE: Which component/module/file type implements this (e.g., "in the Chrome extension content script", "in the Express.js API controller", "in the React settings panel")
2. WHAT TRIGGERS IT: User action or system event that initiates this feature
3. HOW IT WORKS: The technical flow and user interaction details
4. INTEGRATION POINTS: What APIs it calls, what data it sends/receives, what databases it updates
5. USER VALUE: What the user accomplishes with this feature

GOOD TASK EXAMPLES (Notice the detail and context):

✓ "We need a way to select starting images to process for the video gen service.  In the Chrome extension content script, implement right-click context menu that detects when users right-click on any image element (including CSS background images). Add a 'Generate Video with AI' option to the context menu that, when selected, captures the image URL and displays an overlay modal with a text input for the user's prompt. Upon submission, send both the image URL and prompt text to the backend API endpoint POST /api/submissions, which will handle S3 upload and database storage."

✓ "On extensions option page we need a way to collect votes.  Create the Reddit-style voting interface that displays all video submissions retrieved from GET /api/submissions. Each submission card should show the image thumbnail, prompt text, current vote count, and upvote/downvote buttons. When users click vote buttons, send a POST request to /api/submissions/:id/vote with the vote direction, updating the UI optimistically while preventing duplicate votes per user through local storage tracking."

✓ "Build the daily video generation cron job in the Node.js backend that runs at midnight UTC, queries the MySQL database for the top 12 highest-voted submissions that haven't been generated yet and meet the 2-hour minimum age requirement. For each selected submission, call the Fal.ai image-to-video API with the S3 image URL and user prompt, store the resulting video URL in the database, mark the submission as generated, and send email notifications to the original submitters."

BAD TASK EXAMPLES (too vague, no context):
✗ "Create submission dialog" (Where? How triggered? What does it do?)
✗ "Implement voting system" (Missing all technical details)
✗ "Build the state recovery mechanism in the state management layer that reconstructs system state after unexpected restarts or crashes to ensure research jobs aren't lost. The mechanism loads all non-terminal jobs from persistent storage on startup, validates job integrity and removes corrupted entries, attempts to resume 'researching' status jobs by checking with OpenAI API for completion status, and resets 'pending' jobs that were interrupted mid-clarification. The service sends recovery notifications to affected users explaining any delays and maintains recovery statistics for system reliability monitoring." (Too much jargon word-salad, recovery/validation was outside scope of techspec)
✗ "Build admin panel" (Too broad, no specifics)

THREAD ORGANIZATION EXAMPLES:
- "Chrome Extension Core Features" (content script, background worker, popup UI)
- "Backend API Services" (Express routes, controllers, middleware)
- "Database and Storage" (MySQL schemas, S3 integration, data migrations)
- "Video Generation Pipeline" (Fal.ai integration, queue processing, cost tracking)
- "User Account System" (authentication, credits, purchase flow)

Focus strictly on core functionality needed to meet the requirements - do not add optional enhancements, security features, optimization strategies, or other bells and whistles unless explicitly requested in the requirements.

Save to .claude/spectasks.md in this format:

## Thread Name (Major Feature Area)
- [Detailed 2-4 sentence task description with full context as shown in examples above]
- [Another detailed task description with WHERE, WHAT, HOW, and WHY]

## Another Thread Name  
- [Detailed task description with complete implementation context]
- [Another comprehensive task description]

[Use double line breaks between threads]