write-linear-issue

Creates and updates Linear issues after draft confirmation and read-only verification.

Updated May 18, 2026
One-click install
npx skills add https://github.com/dodonki1223/vault --skill write-linear-issue-dodonki1223
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-linear-issue
Source: https://github.com/dodonki1223/vault/tree/main/.agents/skills/write-linear-issue
Command: npx skills add https://github.com/dodonki1223/vault --skill write-linear-issue-dodonki1223

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing to Linear issues without verification risks wrong targets, malformed descriptions, and accidental changes. This Skill enforces a draft-first workflow so every issue creation or update is reviewed and approved before anything is written to Linear. ## Core Features & Use Cases - Draft-before-write workflow: Presents a structured draft (operation, target, team, title, changes, reason) and writes only after explicit user approval. - Task-type templates: Provides description templates for implementation tasks, investigation tasks, and other requests, with sections like background, goals, completion criteria, and verification steps. - Safe failure handling: Stops on authentication errors (401, OAuth invalid grant), permission issues, or unknown targets, and tells the user exactly what to do next instead of retrying blindly. - Use Case: You ask to create a Linear issue for a bug fix. The Skill verifies the team via a read-only check, shows you a draft with title and structured description, and writes it only after you approve. ## Quick Start Use the write-linear-issue skill to create a new Linear issue in the backend team titled "Fix login timeout" with an implementation task description.

Frequently Asked Questions about write-linear-issue

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

FAQPage Schema
How do I create a Linear issue with an AI agent safely?▼

Use a draft-first workflow: the agent identifies the operation, target team, and changes, verifies the target with a read-only check, then shows a draft for approval. The issue is written to Linear only after you explicitly confirm the draft.

What should a Linear issue description include for implementation tasks?▼

Include sections for background, goal, implementation steps, completion criteria, verification steps, impact scope, related links, and notes. Leave uncertain fields as undecided rather than guessing, and keep the title's content from being repeated at length.

Can this skill fetch Linear issue information instead of writing?▼

No, read-only retrieval is out of scope. For fetching Linear issues, projects, or comments without writing, use the fetch-linear-materials skill instead. This skill only handles create, update, comment, assign, and status or label changes.

What happens when Linear authentication expires during a write?▼

The skill stops immediately on errors like 401 Reauthentication required or oauth_token_invalid_grant and asks you to reauthenticate. It does not attempt alternative write paths or other tools, and retries the same target only after you reauthenticate.

Does it create or update Linear projects and milestones?▼

No, creating or updating Linear Projects and Milestones themselves is explicitly out of scope. It can set an issue's project or milestone field, but it will not modify the project or milestone entities, nor auto-reflect results into project notes.