linear

Create Linear projects and issues via MCP tools with mandatory confirmation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thisguymartin/ai-native-dev --skill linear-thisguymartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/thisguymartin/ai-native-dev/tree/main/.gemini/skills/linear
Command: npx skills add https://github.com/thisguymartin/ai-native-dev --skill linear-thisguymartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes inconsistent and error-prone Linear project and issue creation by enforcing a standardized draft template, mandatory clarification, and confirmation workflow so work items are created correctly and consistently.

Core Features & Use Cases

  • Standardized Draft Template: Always produces the same Linear Issue Creation Template for user review before creating anything.
  • Clarification Protocol: Requires mandatory questions (team, project vs issues, input source, defaults, assignee, disconnected issues) to avoid misconfiguration.
  • MCP Tool Integration: Maps actions to MCP endpoints for creating/updating projects, issues, milestones, labels, comments, and listing teams/users.
  • Multi-Source Input Parsing: Accepts file paths, pasted text, or direct prompts and infers titles, tasks, priorities, and labels.
  • Use Case: Converting stakeholder requests or backlog notes into a verified Linear project with ordered issues and milestones.

Quick Start

Draft a Linear project and ordered issues from this request: Create an onboarding project "New Hire Flow" with three tasks, default team pit-crew, and medium priority.

Frequently Asked Questions about linear

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Linear projects and issues from a text file automatically?

You can create Linear projects by parsing file paths, pasted text, or direct prompts to infer titles, tasks, and priorities. The Skill uses MCP tool integration to map this input into structured Linear issues, requiring your confirmation before actually creating anything.

What is the best way to standardize Linear issue creation across a team?

Standardizing Linear issue creation involves applying a fixed draft template and a mandatory clarification protocol. This enforces consistent data entry by requiring answers about team assignments, input sources, and default priorities before generating the final work items.

Can I convert backlog notes into a verified Linear project with milestones?

Yes, you can convert backlog notes into a verified Linear project by parsing the pasted text to infer tasks and labels. The workflow drafts ordered issues and milestones, using MCP endpoints to save the project only after you explicitly confirm the generated draft.

Does this Linear project setup workflow require specifying a team?

Linear project setup requires specifying a team, but it defaults to the "pit-crew" team if you do not provide one. The mandatory clarification protocol asks about team assignments, disconnected issues, and default settings to ensure accurate configuration before calling MCP tools.

How does mandatory verification work when creating Linear issues via MCP?

Mandatory verification works by generating an Issue Creation Template for your review and asking clarification questions before any MCP tool calls are made. This confirmation workflow prevents inconsistent or error-prone Linear issue creation by enforcing explicit user approval.

What are the limitations of using automated templates for Linear issue tracking?

A limitation of automated templates for Linear issue tracking is the mandatory clarification step, which requires answering questions about assignees and projects before creation. Additionally, this workflow relies on MCP-integrated environments to execute the tool calls for saving milestones and listing users.