linear-dev-accelerator_skill

Overview

This skill accelerates software development by combining Linear project management with MCP server tools for fast issue tracking, project setup, and workflow automation. It helps teams manage frontend, backend, and mobile work with patterns for features, bugs, cycles, and GitHub integration. Use it to standardize processes, reduce context switching, and keep velocity high.

How this skill works

The skill exposes MCP commands to list, create, update, and query Linear entities (issues, projects, labels, cycles, documents, comments, teams, and users). It maps common development patterns—feature development, bug triage, sprint planning, and GitHub PR linking—into repeatable workflows and automation steps. Use the provided parameters and examples to filter results, create rich issues, organize cycles, and sync branches/PRs to Linear issues.

When to use it

• Starting a new frontend, backend, or mobile project and need project scaffolding in Linear
• Managing and triaging bugs, features, and technical debt across teams
• Planning and running time-boxed cycles/sprints with clear issue assignments
• Linking Linear issues to GitHub branches and PRs for traceability
• Automating repeated project management tasks and batch issue creation
• Keeping cross-functional teams aligned with consistent workflows and labels

Best practices

• Create issues with clear titles, acceptance criteria, and task checklists to reduce back-and-forth
• Use consistent labels and naming conventions (teams, projects, label colors) for reliable filtering and reporting
• Break large features into child issues with parentId to keep work bite-sized and track progress
• Assign issues and set realistic priorities to balance workload across team members each cycle
• Use Git branch names from Linear and reference issue IDs in commits/PRs to enable automatic linking and state transitions

Example use cases

• New feature rollout: create a parent feature issue, spawn sub-tasks, assign owners, place in cycle, and track to Done
• Bug triage: create reproducible bug issues with logs/screenshots, investigate, link fixes via PR, and verify in QA before closing
• Sprint planning: list backlog issues, pick ready items, create a cycle, assign and balance priorities across team members
• Project kickoff: create project with summary, set lead, dates, labels, create initial setup issues and epics
• GitHub integration: use Linear’s suggested gitBranchName, create branch, open PR, and let Linear auto-update issue state