speckit.linear.export

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

1. Validate prerequisites:

   • Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
   • Parse FEATURE_DIR and verify tasks.md exists
   • Extract Linear ID from spec.md frontmatter (if imported via /speckit.linear.import)

2. Determine parent Linear issue:

   • If spec has linear_id in frontmatter, use that
   • If user provided issue ID in arguments, use that
   • Otherwise, ask: "Which Linear issue should these tasks be linked to? (e.g., TEAM-123)"

3. Parse tasks.md:

   • Extract all tasks with their metadata:
     • Task ID (e.g., T001)
     • Description
     • Priority (P1/P2/P3)
     • Phase (Setup/Tests/Core/Integration/Polish)
     • File paths affected
     • Dependencies
     • Parallel marker [P]

4. Map priorities to Linear:

   Spec Kit	Linear Priority
   P1	Urgent (1)
   P2	High (2)
   P3	Medium (3)

5. Create sub-issues in Linear for each task:

   • Use mcp__linear__create_issue for each task
   • Set parent issue relationship
   • Include in description:

     ## Task Details
     - **Spec Kit ID**: T001
     - **Phase**: Core
     - **Files**: src/auth/login.ts, src/auth/session.ts
     - **Dependencies**: T000 (setup)
     
     ## Description
     [Task description from tasks.md]
     
     ---
     _Auto-generated by Spec Kit from specs/002-feature/tasks.md_
     

6. Track created issues:

   • Update tasks.md with Linear issue IDs:

     - [x] T001: Implement login endpoint <!-- LINEAR:TEAM-124 -->
     

   • Create/update .specify/linear-mapping.json:

     {
       "feature": "002-user-authentication",
       "parent_issue": "TEAM-123",
       "tasks": {
         "T001": "TEAM-124",
         "T002": "TEAM-125"
       },
       "exported_at": "2025-01-15T10:30:00Z"
     }