linear-workflow

Guide Linear project and issue management with cycle reviews and API instructions.

1|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/ryosukesuto/dotfiles --skill linear-workflow-ryosukesuto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-workflow
Source: https://github.com/ryosukesuto/dotfiles/tree/main/config/claude/skills/linear-workflow
Command: npx skills add https://github.com/ryosukesuto/dotfiles --skill linear-workflow-ryosukesuto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured workflow for managing tasks and projects in Linear, transforming it into a decision-making log and ensuring efficient cycle management.

Core Features & Use Cases

  • Project & Issue Creation Guidelines: Defines criteria for creating projects and issues, including essential fields and descriptions.
  • Cycle Management: Outlines weekly and cycle review processes, focusing on project progress and decision-making.
  • Point Estimation: Offers a clear guideline for estimating task effort.
  • Linear API Usage: Provides specific instructions for interacting with the Linear API, especially regarding cycle and team IDs.
  • Use Case: A development team can use this Skill to ensure all new features are properly scoped as Linear projects, issues are clearly defined with "why" and "what not to do," and weekly reviews focus on project blockers and intentional "not-to-do" decisions.

Quick Start

Follow the guidelines in this skill to create a new Linear issue for a bug report, ensuring all required fields like 'Team', 'Assignee', and 'Estimate' are correctly set.

Frequently Asked Questions about linear-workflow

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

FAQPage Schema
How do I structure Linear issue creation to include decision-making logs?

To structure Linear issue creation effectively, define the "why" and "what not to do" in descriptions, and ensure required fields like Team, Assignee, and Estimate are set. This transforms issues into clear decision-making logs.

What guidelines should I follow for Linear cycle management and weekly reviews?

Linear cycle management involves running weekly reviews focused on project blockers and intentional "not-to-do" decisions. This ensures efficient cycle management by tracking project progress and maintaining clear decision logs.

How do I estimate task effort for issues in Linear?

You estimate task effort in Linear by applying a specific point estimation guideline provided within the workflow. This offers a clear, structured approach to assigning accurate effort estimates to your project issues.

How do I use the Linear API for team and cycle ID management?

The Linear API can be used for team and cycle ID management by following specific instructions for interacting with API endpoints. This ensures accurate retrieval and mapping of cycle and team identifiers for automation.

What are the criteria for creating a new project versus an issue in Linear?

Creating a Linear project requires properly scoping new features, while issue creation demands clear definitions of the problem and boundaries. Both processes have specific criteria and essential fields that must be populated.