linear-task-management

Standardize Linear issue creation, naming, priorities, and status transitions.

59|12|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/etylsarin/opencastle --skill linear-task-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-task-management
Source: https://github.com/etylsarin/opencastle/tree/main/src/orchestrator/plugins/linear
Command: npx skills add https://github.com/etylsarin/opencastle --skill linear-task-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent issue naming, labels, priorities, and status transitions can fragment work across teams and agents and make feature decomposition, parallel execution, and session resumption unreliable. This Skill provides a clear, repeatable set of conventions and workflows that ensure issues are created, tracked, and transitioned consistently on a Linear board so agents and humans can coordinate without stepping on each other's changes.

Core Features & Use Cases

  • Naming & Partitioning: Standard area-prefixed issue titles and a Files (partition) section to prevent overlapping file edits when multiple agents work in parallel.
  • Priority & Status Workflow: Defined priority levels and a status lifecycle that maps agent-driven transitions and GitHub PR automations to Linear states.
  • Bug & Session Handling: Guidance for capturing discovered issues, creating tracked bug tickets, and resuming interrupted sessions by reading In Progress and Todo issues.
  • MCP Integration: Works with an MCP connector to create, list, get, update, and search issues programmatically and relies on a Linear API key for authentication.

Quick Start

Use the linear-task-management skill to decompose a new feature into Linear issues with area-prefixed names, labels, priorities, acceptance criteria, and Files partitions so agents can be assigned without overlap.

Frequently Asked Questions about linear-task-management

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

FAQPage Schema
How do I standardize Linear issue naming and status management for feature work?

Standardize Linear issue naming by applying area-prefixed titles, defined priority levels, and a status lifecycle that maps agent transitions and GitHub PR automations to Linear states. This prevents fragmented work and overlapping file edits across teams and agents.

Do I need an MCP connector and a Linear API key to automate issue tracking?

Yes, you need a Linear personal API key and an MCP connector to create, list, get, update, and search issues programmatically. This integration enforces naming, priority, and status conventions while authenticating automated Linear board updates.

How do I resume an interrupted multi-agent task management session in Linear?

Resume interrupted multi-agent sessions by reading In Progress and Todo issues on the Linear board. This relies on the standardized status lifecycle and Files partition sections to restore context and prevent overlapping file edits when agents resume work.

What's the best way to prevent overlapping file edits when multiple agents work in parallel?

Prevent overlapping file edits by assigning area-prefixed issue titles and using a Files partition section during feature decomposition. This standardizes task management so agents coordinate reliably without stepping on each other's changes.

Can I link GitHub PR status automations to Linear issue transitions?

Yes, you can link GitHub PR automations to Linear issue transitions using the defined status lifecycle. This maps agent-driven state changes and PR updates directly to Linear states, ensuring consistent issue tracking across development workflows.

How do I track discovered bugs during feature decomposition in Linear?

Track discovered bugs during feature decomposition by creating tracked bug tickets in Linear using the MCP connector. This enforces consistent priority and status conventions for captured issues alongside standard feature work.