Linear Dev Accelerator

Linear Development Accelerator

A comprehensive skill for accelerating software development using Linear project management with MCP server integration. This skill enables rapid project setup, intelligent issue management, and streamlined development workflows for web and mobile applications.

When to Use This Skill

Use this skill when:

• Starting a new software development project and need to set up Linear project management
• Managing issues, tasks, and features for frontend, backend, or full-stack applications
• Organizing development work into sprints/cycles with proper tracking
• Collaborating with development teams on software projects
• Automating project management tasks during development
• Tracking bugs, features, and technical debt systematically
• Building applications with structured project management workflows
• Integrating Linear with GitHub for PR-based development

Core Concepts

Linear Project Management Philosophy

Linear emphasizes speed, clarity, and focus for software teams:

• Issues as First-Class Citizens: Every unit of work is an issue with rich metadata
• Cycles for Sprint Planning: Time-boxed iterations for focused execution
• Projects for Product Planning: Higher-level initiatives and roadmaps
• Teams for Organization: Workspaces for different functions or products
• Workflows for Process: Custom statuses matching your development process

Key Linear Entities

1. Teams: Organizational units (e.g., Frontend, Backend, Mobile)
2. Issues: Individual tasks, bugs, features, or improvements
3. Projects: Collections of related issues for larger initiatives
4. Cycles: Time-boxed iterations (similar to sprints)
5. Labels: Categorization and filtering mechanism
6. Statuses: Issue states (Backlog, Todo, In Progress, In Review, Done, Canceled)
7. Comments: Collaboration and discussion on issues
8. Documents: Long-form documentation integrated with issues

MCP Server Tools Reference

Issue Management

list_issues

List and filter issues in your workspace.

Common Parameters:

team: Team name or ID
assignee: User ID, name, email, or "me" for your issues
state: Status name or ID (e.g., "In Progress", "Done")
label: Label name or ID for filtering
project: Project name or ID
query: Search in title/description
limit: Number of results (max 250, default 50)
orderBy: "createdAt" or "updatedAt" (default)
includeArchived: Include archived issues (default: true)

Examples:

# Get my current issues
assignee: "me"
state: "In Progress"
limit: 10

# Find bugs in a specific project
label: "bug"
project: "Mobile App"
state: "Todo"

# Search for authentication-related issues
query: "authentication"
team: "Backend"

create_issue

Create a new issue with full metadata.

Required Parameters:

title: Issue title (clear and concise)
team: Team name or ID

Optional Parameters:

description: Markdown description with details
assignee: User ID, name, email, or "me"
state: State type, name, or ID
priority: 0=None, 1=Urgent, 2=High, 3=Normal, 4=Low
labels: Array of label names or IDs
project: Project name or ID
cycle: Cycle name, number, or ID
parentId: Parent issue ID for sub-issues
dueDate: ISO format date
links: Array of {url, title} objects

Example:

title: "Implement user authentication"
team: "Backend"
description: |
  ## Overview
  Add JWT-based authentication to the API

  ## Tasks
  - [ ] Design auth flow
  - [ ] Implement JWT tokens
  - [ ] Add refresh token logic
  - [ ] Write tests

  ## Acceptance Criteria
  - Secure token generation
  - Token expiration handling
  - Proper error responses
assignee: "me"
priority: 2  # High
labels: ["feature", "authentication", "backend"]
project: "API v2.0"

update_issue

Update an existing issue.

Required: id (issue ID)

Updatable Fields:

title, description, assignee, state, priority, labels,
project, cycle, parentId, dueDate, estimate, links

Example:

id: "issue-uuid-here"
state: "In Progress"
assignee: "me"
labels: ["feature", "in-development"]

get_issue

Get detailed issue information including attachments and git branch.

Parameters:

id: Issue ID

Returns: Full issue details with attachments, git branch name, related data

Project Management

list_projects

List and filter projects.

Parameters:

team: Team name or ID
state: State name or ID
member: User ID, name, email, or "me"
initiative: Initiative name or ID
query: Search project names
limit: Number of results (max 250, default 50)
orderBy: "createdAt" or "updatedAt"
includeArchived: Include archived (default: false)

create_project

Create a new project.

Required Parameters:

name: Project name
team: Team name or ID

Optional Parameters:

description: Full Markdown description
summary: Concise plaintext summary (max 255 chars)
lead: Project lead (User ID, name, email, or "me")
state: Project state
priority: 0-4 (None, Urgent, High, Medium, Low)
startDate: ISO format date
targetDate: ISO format date
labels: Array of label names or IDs

Example:

name: "Mobile App v2.0"
team: "Mobile"
summary: "Complete redesign of mobile app with new features"
description: |
  # Mobile App v2.0

  ## Goals
  - Modern UI/UX redesign
  - Offline-first architecture
  - Push notifications
  - Real-time sync

  ## Timeline
  Q1 2025 - Design & Planning
  Q2 2025 - Development
  Q3 2025 - Testing & Launch
lead: "me"
priority: 2
startDate: "2025-01-15"
targetDate: "2025-09-30"
labels: ["mobile", "redesign", "major-release"]

update_project

Update existing project details.

Required: id (project ID)

Updatable: name, description, summary, lead, state, priority, startDate, targetDate, labels

get_project

Get detailed project information.

Parameters:

query: Project ID or name

Labels & Categorization

list_issue_labels

List available labels.

Parameters:

team: Team name or ID (optional, for team-specific labels)
name: Filter by label name
limit: Number of results (max 250)
orderBy: "createdAt" or "updatedAt"

create_issue_label

Create new label for categorization.

Required:

name: Label name

Optional:

color: Hex color code (e.g., "#10B981")
description: Label description
teamId: Team UUID (omit for workspace label)
isGroup: true for label groups (default: false)
parentId: Parent label UUID for hierarchical labels

Example:

name: "frontend"
color: "#3B82F6"
description: "Frontend-related tasks and features"
teamId: "team-uuid-here"

Workflow & Status Management

list_issue_statuses

List available statuses for a team.

Parameters:

team: Team name or ID (required)

Returns: Array of statuses with id, type, name

• Types: backlog, unstarted, started, completed, canceled

get_issue_status

Get detailed status information.

Parameters:

id: Status ID
name: Status name
team: Team name or ID (required)

Collaboration

list_comments

List comments on an issue.

Parameters:

issueId: Issue ID (required)

create_comment

Add comment to an issue.

Parameters:

issueId: Issue ID (required)
body: Markdown comment content (required)
parentId: Parent comment ID for replies (optional)

Example:

issueId: "issue-uuid-here"
body: |
  Great progress! A few notes:

  - Consider edge case for expired tokens
  - Add integration test for refresh flow
  - Document the auth header format

Team & User Management

list_teams

List all teams in workspace.

Parameters:

query: Search query (optional)
limit: Number of results (max 250)
includeArchived: Include archived teams (default: false)

get_team

Get detailed team information.

Parameters:

query: Team UUID, key, or name

list_users

List users in workspace.

Parameters: