linear-create

Create Linear issues, projects, initiatives, and project updates from planning documents.

4|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/alexanderguy/skills --skill linear-create-alexanderguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-create
Source: https://github.com/alexanderguy/skills/tree/main/skills/linear-create
Command: npx skills add https://github.com/alexanderguy/skills --skill linear-create-alexanderguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns ambiguous feature scope or a rough planning document into well-structured Linear artifacts, so teams spend less time figuring out what to create and more time aligning on outcomes and next steps.

Core Features & Use Cases

  • Detects the right artifact type (issue vs project vs initiative, plus explicit support for project updates when requested).
  • Finds and uses planning documents from common repo locations to pre-populate scope, context, and constraints, then prompts only for missing details.
  • Interviews for missing inputs to produce handoff-ready drafts with acceptance criteria and outcome-focused descriptions.
  • Creates artifacts in Linear with correct relationships including dependency ordering and linking issues into projects/initiatives.
  • Supports document attachments by uploading relevant specs to the created artifacts instead of referencing local paths.

Quick Start

Tell it what you want to create (issue, project, initiative, or an explicit project update) and optionally include --from-doc to base the draft on PRODUCT.md, ARCHITECTURE.md, or IMPLEMENTATION.md.

Frequently Asked Questions about linear-create

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

FAQPage Schema
How do I create Linear issues from a planning document?

You can create Linear issues from planning documents by using the --from-doc option, which extracts scope and constraints from files like PRODUCT.md, ARCHITECTURE.md, or IMPLEMENTATION.md to pre-populate outcome-driven artifacts.

How do I structure Linear projects with dependency-aware tasks?

Structuring Linear projects with dependency-aware tasks involves mapping larger work into properly sized issues, establishing correct dependency ordering, and linking issues into projects or initiatives to ensure clear execution paths.

Can I generate Linear project updates from feature scope?

Yes, you can generate explicit Linear project updates from feature scope. The system detects when an update is requested, extracts context from planning files, and drafts an outcome-focused update for the workspace.

Does creating Linear artifacts require a Linear MCP tool?

Yes, creating Linear artifacts through this method requires the Linear MCP tool. The workflow validates Linear MCP tool availability before drafting descriptions and creating linked artifacts in the workspace.

How do I attach planning specs to Linear issues?

To attach planning specs to Linear issues, the system uploads relevant specification documents directly to the created artifacts, preserving the specs within the workspace instead of merely referencing local file paths.

What is the best way to map roadmap items to Linear initiatives?

The best way to map roadmap items to Linear initiatives is to extract outcome-focused context from planning documents, confirm the initiative type, and create dependency-aware artifacts linked correctly within the Linear workspace.