Skip to main content

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:
Expected Output: List of teams in workspace Record: Team IDs and names

Step 1.2: Get Team Details

Command (for each team):
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:
Command:
Command:
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:
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:
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:
Record: EPIC_PHOTO_MGMT_ID

Epic 2: AI Journaling Engine

Command:
Record: EPIC_AI_ENGINE_ID

Epic 3: Emotion Tagging

Command:
Record: EPIC_EMOTION_TAG_ID

Epic 4: Timeline View

Command:
Record: EPIC_TIMELINE_ID

Epic 5: Entry Detail View

Command:
Record: EPIC_ENTRY_DETAIL_ID

Epic 6: Search & Filter

Command:
Record: EPIC_SEARCH_FILTER_ID

Epic 7: Authentication & Profile

Command:
Record: EPIC_AUTH_PROFILE_ID

Epic 8: Onboarding

Command:
Record: EPIC_ONBOARDING_ID

Epic 9: Settings & Preferences

Command:
Record: EPIC_SETTINGS_ID

Epic 10: Freemium Gates

Command:
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):
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):
Add comment to note dependencies:

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:

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:

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.