> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentsoflearning.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear execution guide

# Linear Execution Guide: Audit & Issue Creation

**Date**: 2025-11-10
**Purpose**: Step-by-step guide to audit Linear and create all MVP issues
**Owner**: Senior Product Manager

***

## Overview

This guide provides commands to:

1. Audit current Linear state
2. Create Q1 2025 MVP project structure
3. Create all 10 epics and 63+ feature issues
4. Set up dependencies and relationships

***

## Phase 1: Audit Current State

### Step 1.1: List All Teams

**Command**:

```bash theme={null}
mcp__linear__list_teams
```

**Expected Output**: List of teams in workspace
**Record**: Team IDs and names

***

### Step 1.2: Get Team Details

**Command** (for each team):

```bash theme={null}
mcp__linear__get_team
  team_id: <TEAM_ID_FROM_STEP_1>
```

**Expected Output**: Team details including:

* Available states (Backlog, Todo, In Progress, Done, etc.)
* State IDs
* Workflow configuration

**Record**: State IDs for issue creation

***

### Step 1.3: Search Existing Issues

**Command**:

```bash theme={null}
mcp__linear__search_issues
  query: "MVP"
  limit: 50
```

**Command**:

```bash theme={null}
mcp__linear__search_issues
  query: "Q1 2025"
  limit: 50
```

**Command**:

```bash theme={null}
mcp__linear__search_issues
  query: "photo journal"
  limit: 50
```

**Purpose**: Check if any issues already exist for this project

**Record**:

* Existing issue count
* Existing issue IDs and titles
* Any conflicts or duplicates

***

### Step 1.4: List Existing Projects

**Command**:

```bash theme={null}
mcp__linear__list_projects
```

**Expected Output**: List of all projects
**Record**: Project names and IDs

***

## Phase 2: Create Project Structure

### Step 2.1: Create Q1 2025 MVP Launch Project

**Command**:

```bash theme={null}
mcp__linear__create_project
  name: "Q1 2025 MVP Launch"
  description: "AI-powered photo journaling iOS app - MVP launch. Target: April 2025. Goal: 5,000 users, 60% D30 retention, 5% conversion."
  team_id: <TEAM_ID>
  target_date: "2025-04-15"
```

**Expected Output**: Project created with ID
**Record**: PROJECT\_ID for linking issues

***

## Phase 3: Create Epic-Level Issues (10 Epics)

### Epic 1: Photo Management

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Photo Management"
  description: "## Overview
Complete photo lifecycle management including camera capture, library selection, basic editing, and cloud storage.

## User Stories
- 1.1: Capture Photo with In-App Camera (3 pts)
- 1.2: Select Photo from Library (2 pts)
- 1.3: Basic Photo Editing (5 pts)
- 1.4: Photo Upload to Cloud Storage (5 pts)

**Total Estimate**: 15 story points

## Acceptance Criteria
- [ ] Users can capture photos in-app or select from library
- [ ] Basic crop and rotate editing available
- [ ] Photos upload to cloud storage reliably
- [ ] Upload queue handles failures gracefully

## Dependencies
None (foundational epic)

## Technical Stack
- iOS: AVFoundation for camera
- iOS: PHPickerViewController for library
- Backend: AWS S3 or GCP Cloud Storage
- Compression: iOS native APIs

## Phase
Phase 1 - Foundation (Weeks 1-3)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Photo Management (Lines 83-176)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_PHOTO\_MGMT\_ID

***

### Epic 2: AI Journaling Engine

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] AI Journaling Engine"
  description: "## Overview
AI-powered journaling features including prompt suggestions, emotion detection, and free-form text entry.

## User Stories
- 2.1: AI-Generated Prompt Suggestions (8 pts)
- 2.2: One-Tap Prompt Selection (3 pts)
- 2.3: Free-Form Text Entry (2 pts)
- 2.4: AI-Suggested Emotions (5 pts)

**Total Estimate**: 18 story points

## Acceptance Criteria
- [ ] AI generates 3 relevant prompts per photo within 5 seconds
- [ ] Users can select prompts with one tap
- [ ] Free-form text entry supports up to 500 characters (free tier)
- [ ] AI suggests 2-3 emotions based on photo and text

## Dependencies
- Backend API for AI integration
- OpenAI or similar AI service integration

## Technical Stack
- AI: OpenAI GPT-4 API (or Claude, or open-source)
- Backend: AI integration service
- Frontend: Real-time UI updates
- Caching: Prompt cache to reduce API costs

## Phase
Phase 2 - Core Journaling (Weeks 4-6)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: AI Journaling Engine (Lines 178-272)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_AI\_ENGINE\_ID

***

### Epic 3: Emotion Tagging

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Emotion Tagging"
  description: "## Overview
Emotion taxonomy system with visual display and multi-select capabilities.

## Emotion Taxonomy (12 emotions)
**Positive (4)**: Happy, Grateful, Excited, Peaceful
**Reflective (4)**: Thoughtful, Nostalgic, Proud, Loving
**Challenging (4)**: Sad, Anxious, Frustrated, Hopeful

## User Stories
- 3.1: Predefined Emotion Taxonomy (0 pts - documentation)
- 3.2: Multi-Select Emotion Tags (3 pts)
- 3.3: Visual Emotion Display (3 pts)
- 3.4: Edit and Remove Emotion Tags (2 pts)

**Total Estimate**: 11 story points (8 pts implementation)

## Acceptance Criteria
- [ ] All 12 emotions available throughout app
- [ ] Users can select multiple emotions per entry
- [ ] Emotions display with icons and colors
- [ ] Users can edit/remove emotions after entry creation

## Dependencies
- Design system for emotion icons and colors
- Marketer + UX Designer for brand-aligned emotion colors

## Technical Stack
- Database: Emotions table with taxonomy
- Frontend: Multi-select component
- Design: Icon set + color palette

## Phase
Phase 1 (taxonomy), Phase 2 (implementation)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Emotion Tagging (Lines 274-379)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_EMOTION\_TAG\_ID

***

### Epic 4: Timeline View

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Timeline View"
  description: "## Overview
Main browsing experience with photo grid, date navigation, and pull-to-refresh.

## User Stories
- 4.1: Chronological Photo Grid (5 pts)
- 4.2: Date Navigation (5 pts)
- 4.3: Entry Preview on Timeline (3 pts)
- 4.4: Pull-to-Refresh (2 pts)

**Total Estimate**: 15 story points

## Acceptance Criteria
- [ ] Entries display in reverse chronological grid
- [ ] Users can navigate by date (month/year picker)
- [ ] Each entry shows photo, date, emotions, text preview
- [ ] Pull-to-refresh syncs latest entries

## Dependencies
- Photo Management (Epic 1) - photos to display
- Emotion Tagging (Epic 3) - emotions to show
- Backend API - entries endpoint

## Technical Stack
- Frontend: Collection View (iOS) with custom layout
- Layout: 2 columns portrait, 3 columns landscape
- Performance: Image caching and lazy loading
- Navigation: Date picker component

## Phase
Phase 2 - Core Journaling (Weeks 4-6)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Timeline View (Lines 381-472)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_TIMELINE\_ID

***

### Epic 5: Entry Detail View

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Entry Detail View"
  description: "## Overview
Full entry viewing experience with photo, text, emotions, and edit/delete options.

## User Stories
- 5.1: Full-Size Photo Display (3 pts)
- 5.2: Complete Journal Text Display (2 pts)
- 5.3: Emotion Tags and Metadata Display (3 pts)
- 5.4: Edit and Delete Options (3 pts)

**Total Estimate**: 11 story points

## Acceptance Criteria
- [ ] Full-size photo with pinch-to-zoom
- [ ] Complete journal text with formatting preserved
- [ ] All emotions and metadata visible
- [ ] Users can edit or delete entries with confirmation

## Dependencies
- Timeline View (Epic 4) - navigation to detail
- Emotion Tagging (Epic 3) - emotion display
- Backend API - entry CRUD operations

## Technical Stack
- Frontend: Scroll view with image zoom
- Image: High-resolution photo display
- Text: Multi-line text view with accessibility
- Actions: Edit/delete with confirmation dialogs

## Phase
Phase 3 - Details & Search (Weeks 7-9)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Entry Detail View (Lines 474-565)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_ENTRY\_DETAIL\_ID

***

### Epic 6: Search & Filter

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Search & Filter"
  description: "## Overview
Search and filter capabilities for finding specific entries by keyword, date, or emotion.

## User Stories
- 6.1: Keyword Search (Text Content) (5 pts)
- 6.2: Date Range Filter (5 pts)
- 6.3: Emotion Filter (4 pts) - **OR logic approved**
- 6.4: Display Search Results (3 pts)

**Total Estimate**: 17 story points

## Acceptance Criteria
- [ ] Users can search journal text by keyword
- [ ] Date range filters with presets and custom range
- [ ] Emotion filters use OR logic (any selected emotion)
- [ ] Results display in timeline grid format with result count

## Key Decision: Emotion Filter OR Logic
**Approved in PRD**: Emotion filter uses OR logic
- Select \"Happy\" + \"Grateful\" → shows entries with Happy OR Grateful OR both
- Rationale: More inclusive, helps users find memories

## Dependencies
- Timeline View (Epic 4) - results display
- Emotion Tagging (Epic 3) - emotion filtering
- Backend API - search and filter endpoints

## Technical Stack
- Backend: Full-text search (PostgreSQL or Elasticsearch)
- Frontend: Search bar + filter UI
- Database: Indexed columns for performance
- Query: Combined filters with AND logic across types

## Phase
Phase 3 - Details & Search (Weeks 7-9)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Search & Filter (Lines 567-659)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_SEARCH\_FILTER\_ID

***

### Epic 7: Authentication & Profile

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Authentication & Profile"
  description: "## Overview
User authentication system with email, Apple Sign-In, and profile management.

## User Stories
- 7.1: Email Signup (5 pts)
- 7.2: Email Login (3 pts)
- 7.3: Apple Sign-In (Social Login) (5 pts)
- 7.4: Password Reset (5 pts)
- 7.5: Basic Profile Settings (4 pts)

**Total Estimate**: 22 story points

## Acceptance Criteria
- [ ] Users can sign up with email and password
- [ ] Users can log in with email or Apple Sign-In
- [ ] Password reset via email works reliably
- [ ] Users can update profile name and password
- [ ] Account deletion available with confirmation

## Dependencies
None (foundational epic)

## Technical Stack
- Backend: JWT authentication
- Auth Service: Auth0, Firebase Auth, or custom
- iOS: Sign in with Apple (required by Apple guidelines)
- Security: bcrypt password hashing, rate limiting
- Email: Transactional email service (SendGrid, AWS SES)

## Phase
Phase 1 - Foundation (Weeks 1-3)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Authentication & Profile (Lines 661-778)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_AUTH\_PROFILE\_ID

***

### Epic 8: Onboarding

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Onboarding"
  description: "## Overview
First-time user experience with welcome screens, how-it-works, and permissions.

## User Stories
- 8.1: Welcome Screen (Screen 1 of 3) (3 pts)
- 8.2: How It Works (Screen 2 of 3) (2 pts)
- 8.3: Permissions Request (Screen 3 of 3) (4 pts)
- 8.4: First Entry Guidance (3 pts)

**Total Estimate**: 12 story points

## Acceptance Criteria
- [ ] 3-screen onboarding explains value proposition
- [ ] Camera and notification permissions requested clearly
- [ ] First entry guidance helps users succeed
- [ ] Empty state inspires action

## Dependencies
- Authentication (Epic 7) - post-auth onboarding
- Timeline View (Epic 4) - completes to timeline

## Technical Stack
- Frontend: Page view controller (iOS)
- Permissions: AVFoundation (camera), UserNotifications
- Design: Branded screens with illustrations
- Copy: Warm, welcoming, clear value

## Phase
Phase 3 - Details & Search (Weeks 7-9)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Onboarding (Lines 780-872)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_ONBOARDING\_ID

***

### Epic 9: Settings & Preferences

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Settings & Preferences"
  description: "## Overview
App settings including account management, notifications, privacy, and help.

## User Stories
- 9.1: Account Settings (4 pts)
- 9.2: Notification Preferences (4 pts)
- 9.3: Privacy Settings (4 pts)
- 9.4: About & Help (3 pts)

**Total Estimate**: 15 story points

## Acceptance Criteria
- [ ] Account management (name, email, password, delete)
- [ ] Daily reminder notifications configurable
- [ ] Privacy controls for location tracking
- [ ] Data export and privacy policy accessible
- [ ] Help, FAQ, and support contact available

## Dependencies
- Authentication (Epic 7) - account to manage

## Technical Stack
- Frontend: Settings UI (iOS native patterns)
- Notifications: UserNotifications framework
- Privacy: Location services toggle, data export
- Legal: Privacy policy and terms pages

## Phase
Phase 4 - Monetization & Polish (Weeks 10-12)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Settings & Preferences (Lines 874-964)"
  team_id: <TEAM_ID>
  priority: 3
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_SETTINGS\_ID

***

### Epic 10: Freemium Gates

**Command**:

```bash theme={null}
mcp__linear__create_issue
  title: "[EPIC] Freemium Gates"
  description: "## Overview
Monetization system with free tier limits, Premium paywall, and in-app purchase flow.

## Pricing Model
- **Free Tier**: 50 photos/month, 500 char/entry
- **Premium**: $8/month or $60/year (save 25%)
- **Free Trial**: 14 days

## User Stories
- 10.1: Free Tier Limits (50 Photos/Month) (5 pts)
- 10.2: Premium Paywall Screen (4 pts)
- 10.3: In-App Purchase Flow (Apple IAP) (6 pts)
- 10.4: Premium Features Unlocked (3 pts)

**Total Estimate**: 18 story points

## Acceptance Criteria
- [ ] Free users limited to 50 photos per calendar month
- [ ] Paywall appears at limit with clear Premium benefits
- [ ] Apple IAP integration working with 14-day free trial
- [ ] Premium users have unlimited photos and visible badge

## Dependencies
- Photo Management (Epic 1) - photo count tracking
- Authentication (Epic 7) - subscription tied to account

## Technical Stack
- iOS: StoreKit 2 for Apple IAP
- Backend: Receipt validation, subscription status
- Database: Subscription tracking, photo count
- Payment: Apple processes all payments

## Phase
Phase 4 - Monetization & Polish (Weeks 10-12)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md
- Epic Section: Freemium Gates (Lines 967-1059)"
  team_id: <TEAM_ID>
  priority: 2
  project_id: <PROJECT_ID>
```

**Record**: EPIC\_FREEMIUM\_ID

***

## Phase 4: Create Feature-Level Issues

### Notes on Feature Issues

* **Total Issues**: 40 user stories + 23 technical issues = 63 issues
* Each issue should be created with:
  * Title format: "Story X.Y: \[Feature Name]" or "LINEAR-X: \[Feature Name]"
  * Full description from implementation plan
  * Parent ID linking to epic
  * Priority, estimate, team labels
  * Acceptance criteria in description

### Example Feature Issue Creation

**Command** (for Story 1.1):

```bash theme={null}
mcp__linear__create_issue
  title: "Story 1.1: Capture Photo with In-App Camera"
  description: "## User Story
**As a** user
**I want** to take photos directly in the app
**So that** I can immediately journal about a moment without switching apps

## Priority
High

## Estimate
3 story points

## Epic
Photo Management (EPIC 1)

## Acceptance Criteria
- [ ] Given I'm on the timeline or create entry screen, when I tap the camera button, then the device camera opens
- [ ] Given the camera is open, when I tap the capture button, then a photo is taken and displayed for review
- [ ] Given I've taken a photo, when I tap \"Use Photo\", then I'm taken to the journal entry screen with the photo attached
- [ ] Given I've taken a photo, when I tap \"Retake\", then the camera reopens for another attempt
- [ ] Given the app lacks camera permissions, when I tap the camera button, then I see a permission request dialog

## Technical Notes
- Use native iOS camera API (AVFoundation)
- Support front and rear cameras with toggle
- Include basic flash control
- No video capture in MVP
- Handle permissions gracefully

## Implementation Tasks
- [ ] Set up AVFoundation camera session
- [ ] Create camera view controller
- [ ] Implement capture button logic
- [ ] Handle photo preview UI
- [ ] Implement Use Photo / Retake actions
- [ ] Add permission request handling
- [ ] Test on multiple iOS devices

## Design Requirements
- Camera UI should match brand
- Clear capture button
- Preview screen with action buttons
- Permission dialog should explain why camera is needed

## Backend Dependencies
None (frontend only)

## Related Documentation
- PRD: /docs/product/prds/mvp-q1-2025-prd.md (Lines 85-105)
- Linear Implementation Plan: /docs/product/linear-implementation-plan.md

## Phase
Phase 1 - Foundation (Weeks 1-3)"
  team_id: <TEAM_ID>
  priority: 2
  parent_id: <EPIC_PHOTO_MGMT_ID>
  project_id: <PROJECT_ID>
```

**Record**: LINEAR\_1\_ID

***

### Batch Creation Strategy

**Recommended Approach**:

1. Create all 10 epics first (record IDs)
2. Create feature issues in epic order
3. Link each feature issue to parent epic
4. Add dependencies between issues as needed

**Issue Naming Convention**:

* Epics: "\[EPIC] Epic Name"
* User Stories: "Story X.Y: Feature Name"
* Technical Issues: "LINEAR-XX: Feature Name"

***

## Phase 5: Set Up Relationships & Dependencies

### Parent-Child Relationships

Already set during creation via `parent_id` parameter.

### Cross-Epic Dependencies

**Command** (example):

```bash theme={null}
mcp__linear__update_issue
  issue_id: <EPIC_TIMELINE_ID>
  description: "[Updated description with dependencies noted]"
```

**Add comment to note dependencies**:

```bash theme={null}
mcp__linear__add_comment
  issue_id: <EPIC_TIMELINE_ID>
  body: "## Dependencies

**Blocked by**:
- EPIC: Photo Management (must have photos to display)
- EPIC: Emotion Tagging (must have emotions to show)

**Blocks**:
- EPIC: Entry Detail View (timeline navigates to detail)"
```

***

## Phase 6: Add Labels and Custom Fields

### Labels to Apply

**Epic Labels** (apply to all issues in epic):

* `epic:photo-management`
* `epic:ai-engine`
* `epic:emotion-tagging`
* `epic:timeline`
* `epic:entry-detail`
* `epic:search-filter`
* `epic:auth-profile`
* `epic:onboarding`
* `epic:settings`
* `epic:freemium`

**Phase Labels**:

* `phase:1-foundation`
* `phase:2-core-journaling`
* `phase:3-details-search`
* `phase:4-monetization`
* `phase:5-qa-launch`

**Team Labels**:

* `team:product`
* `team:design`
* `team:backend`
* `team:frontend`
* `team:qa`
* `team:devops`

### Apply Labels Command

**Command**:

```bash theme={null}
mcp__linear__update_issue
  issue_id: <ISSUE_ID>
  labels: ["epic:photo-management", "phase:1-foundation", "team:frontend"]
```

***

## Phase 7: Populate PROJECT\_OVERVIEW\.md

After all issues created, update the project tracking document.

**Update**:

* Linear project URL
* All epic URLs
* Key feature issue URLs
* Current status
* Agent assignments

***

## Audit Report Template

After completing all phases, create an audit report:

```markdown theme={null}
# Linear Audit & Implementation Report

**Date**: 2025-11-10
**Executed By**: Senior Product Manager

---

## Pre-Execution Audit

### Teams Found
- Team Name: [NAME]
- Team ID: [ID]
- Available States: [Backlog, Todo, In Progress, Done, etc.]

### Existing Issues
- Total Issues: [COUNT]
- Relevant to MVP: [COUNT]
- Action: [None / Archived / Updated]

### Existing Projects
- Total Projects: [COUNT]
- Q1 2025 MVP Project: [Existed / Created]

---

## Execution Summary

### Project Created
- **Name**: Q1 2025 MVP Launch
- **ID**: [PROJECT_ID]
- **URL**: [LINEAR_URL]
- **Target Date**: 2025-04-15

### Epics Created (10)
1. [EPIC] Photo Management - [URL]
2. [EPIC] AI Journaling Engine - [URL]
3. [EPIC] Emotion Tagging - [URL]
4. [EPIC] Timeline View - [URL]
5. [EPIC] Entry Detail View - [URL]
6. [EPIC] Search & Filter - [URL]
7. [EPIC] Authentication & Profile - [URL]
8. [EPIC] Onboarding - [URL]
9. [EPIC] Settings & Preferences - [URL]
10. [EPIC] Freemium Gates - [URL]

### Feature Issues Created (63)

#### Epic 1: Photo Management (4 issues)
- LINEAR-1: Story 1.1 - Capture Photo with In-App Camera - [URL]
- LINEAR-2: Story 1.2 - Select Photo from Library - [URL]
- LINEAR-3: Story 1.3 - Basic Photo Editing - [URL]
- LINEAR-4: Story 1.4 - Photo Upload to Cloud Storage - [URL]

[... continue for all 63 issues ...]

### Dependencies Set
- Total dependency links: [COUNT]
- Cross-epic dependencies: [COUNT]

### Labels Applied
- Epic labels: ✅
- Phase labels: ✅
- Team labels: ✅
- Priority labels: ✅

---

## Statistics

### By Epic
| Epic | Issues | Story Points | Priority |
|------|--------|--------------|----------|
| Photo Management | 4 | 15 | High |
| AI Journaling Engine | 4 | 18 | High |
| Emotion Tagging | 4 | 11 | High |
| Timeline View | 4 | 15 | High |
| Entry Detail View | 4 | 11 | High |
| Search & Filter | 4 | 17 | High |
| Authentication & Profile | 5 | 22 | High |
| Onboarding | 4 | 12 | High |
| Settings & Preferences | 4 | 15 | Medium |
| Freemium Gates | 4 | 18 | High |
| **Total User Stories** | **41** | **154** | - |
| Backend API | 7 | 54 | High |
| Database Schema | 5 | 12 | High |
| Infrastructure | 5 | 24 | High |
| QA & Testing | 5 | 30 | High |
| **Total Technical** | **22** | **120** | - |
| **GRAND TOTAL** | **63** | **274** | - |

### By Phase
| Phase | Issues | Story Points |
|-------|--------|--------------|
| Phase 1: Foundation | 15 | 60 |
| Phase 2: Core Journaling | 20 | 85 |
| Phase 3: Details & Search | 15 | 65 |
| Phase 4: Monetization | 8 | 40 |
| Phase 5: QA & Launch | 5 | 24 |

### By Team
| Team | Issues |
|------|--------|
| Frontend | 41 |
| Backend | 15 |
| Design | 41 (dependencies) |
| QA | 5 |
| DevOps | 5 |

---

## Conflicts & Resolutions

### Conflict 1: [If any]
- **Description**: [What conflict was found]
- **Resolution**: [How it was resolved]

[No conflicts encountered if clean slate]

---

## Next Steps

1. ✅ All epics created and documented
2. ✅ All feature issues created with full descriptions
3. ✅ Dependencies and relationships established
4. ✅ Labels and custom fields applied
5. ⏳ **Next**: Assign issues to specific agents (@software-architect, @product-designer, etc.)
6. ⏳ Update PROJECT_OVERVIEW.md with Linear URLs
7. ⏳ Begin Phase 1 work (Authentication + Photo Management + Emotion Taxonomy)

---

## Linear URLs

### Project
- **Q1 2025 MVP Launch**: [URL]

### Epics (Quick Links)
- Photo Management: [URL]
- AI Journaling Engine: [URL]
- Emotion Tagging: [URL]
- Timeline View: [URL]
- Entry Detail View: [URL]
- Search & Filter: [URL]
- Authentication & Profile: [URL]
- Onboarding: [URL]
- Settings & Preferences: [URL]
- Freemium Gates: [URL]

---

**Report Complete**
```

***

## Success Criteria

### Audit Complete ✓

* [ ] All teams listed and IDs recorded
* [ ] All existing issues reviewed
* [ ] No conflicts with existing work
* [ ] Team states and workflows documented

### Project Created ✓

* [ ] Q1 2025 MVP Launch project exists
* [ ] Project linked to correct team
* [ ] Target date set to April 2025

### Epics Created ✓

* [ ] All 10 epics created
* [ ] Each epic has full description
* [ ] Each epic linked to project
* [ ] All epic IDs recorded

### Features Created ✓

* [ ] All 63 feature issues created
* [ ] Each issue has full description with acceptance criteria
* [ ] Each issue linked to parent epic
* [ ] All issue IDs recorded

### Relationships Set ✓

* [ ] Parent-child relationships established
* [ ] Cross-epic dependencies noted
* [ ] Blocking relationships documented

### Labels Applied ✓

* [ ] Epic labels on all issues
* [ ] Phase labels on all issues
* [ ] Team labels on appropriate issues
* [ ] Priority labels on all issues

### Documentation Updated ✓

* [ ] PROJECT\_OVERVIEW\.md updated with Linear URLs
* [ ] Audit report created
* [ ] Next steps clearly defined

***

## Troubleshooting

### Issue: Team ID not found

**Solution**: Run `mcp__linear__list_teams` again and verify team exists

### Issue: Parent ID invalid

**Solution**: Verify epic was created successfully and use correct ID

### Issue: Rate limit hit

**Solution**: Pause for 1 minute, then continue. Linear API has rate limits.

### Issue: Description too long

**Solution**: Shorten description or move details to initial comment

### Issue: State ID not valid

**Solution**: Use `mcp__linear__get_team` to see valid state IDs for team

***

## Execution Checklist

* [ ] Phase 1: Audit current state (Steps 1.1-1.4)
* [ ] Phase 2: Create project (Step 2.1)
* [ ] Phase 3: Create 10 epics (record all IDs)
* [ ] Phase 4: Create 63 feature issues (link to epics)
* [ ] Phase 5: Set up dependencies
* [ ] Phase 6: Apply labels
* [ ] Phase 7: Update PROJECT\_OVERVIEW\.md
* [ ] Phase 8: Create audit report
* [ ] Phase 9: Assign issues to agents
* [ ] Phase 10: Begin Phase 1 development

***

**This execution guide is ready. Proceed with Linear MCP tool execution.**
