PM/Linear Skill
Purpose
Assist with product management workflows: writing tickets, triaging bugs, updating priorities, and managing work in Linear.
When to Activate
Activate this skill when the user:
- •Asks to write, create, or draft a ticket/issue/story
- •Wants to triage or categorize bugs
- •Discusses prioritization or backlog management
- •References Linear or ticket management
- •Asks for help with product specs or requirements
- •Wants to create or manage projects/roadmap items
- •Asks to review roadmap health or status
- •Wants to plan an initiative or break down a large feature
- •Wants to start working on something (create ticket-linked branch)
- •Asks to create a branch or start development
Prerequisites
- •Linear MCP server must be configured
- •User should have Linear CLI or MCP access
- •Workspace config synced (auto-prompted if missing/stale)
Workspace Config
This skill uses a local cache of your Linear workspace metadata for accurate suggestions.
Location: .claude/linear-workspace.json
Auto-sync behavior:
- •Missing config → prompt to sync on first ticket creation
- •Config >7 days old → prompt to refresh
- •User says "sync linear" → force refresh
- •Label/project not found → suggest refresh
See cookbook/workspace-config.md for details.
Variables
- •
$TICKET_TYPE: bug | feature | chore | improvement - •
$PRIORITY: urgent | high | medium | low - •
$TEAM: The Linear team/project identifier - •
$CONTEXT: Relevant codebase or conversation context
Workflow
Before Any Operation
- •Check for
.claude/linear-workspace.json - •If missing or stale (>7 days), run
prompts/sync-workspace.md - •Load workspace labels, teams, projects, states for suggestions
For Writing New Tickets
- •Determine ticket type from context (bug, feature, chore)
- •Read
cookbook/ticket-templates.mdfor the appropriate template - •Read
cookbook/pm-style-guide.mdfor writing conventions - •Draft the ticket following the template
- •Suggest labels/project from workspace config (not generic ones)
- •Ask user to review before creating in Linear
- •Use Linear MCP to create the ticket
For Triaging
- •Read
prompts/triage-bug.md - •Gather information about the issue
- •Suggest priority and categorization using workspace labels
- •Optionally create or update ticket
For Batch Operations
- •Read
prompts/batch-review.md - •Query Linear for relevant tickets
- •Provide summary and recommendations
For Syncing Workspace
- •Read
prompts/sync-workspace.md - •Fetch labels, teams, projects, states, members from Linear MCP
- •Save to
.claude/linear-workspace.json - •Confirm what was synced
For Managing Projects (Roadmap)
- •Read
prompts/manage-project.md - •Create, update, or change status of projects
- •Link issues to projects
- •Set target dates and milestones
For Roadmap Review
- •Read
prompts/roadmap-review.md - •Query all active projects from Linear MCP
- •Analyze health (on track, at risk, blocked)
- •Present summary with recommendations
For Planning Initiatives
- •Read
prompts/plan-initiative.md - •Break down initiative into project + milestones + tickets
- •Draft full plan for review
- •Create project and tickets in Linear if approved
For Starting Work (Ticket-Linked Branches)
- •Read
prompts/start-work.md - •Ensure ticket exists (create via write-ticket if needed)
- •Generate branch name:
{type}/{TICKET_ID}-{description} - •Create branch or worktree
- •Confirm setup with next steps
Cookbook (Progressive Disclosure)
Only read these when relevant:
- •User asks about templates →
cookbook/ticket-templates.md - •User asks about style →
cookbook/pm-style-guide.md - •User asks about Linear specifics →
cookbook/linear-patterns.md - •User asks about workspace config →
cookbook/workspace-config.md - •User asks about roadmaps/projects →
cookbook/roadmap-patterns.md
Integration
This skill composes with the Linear MCP server. Ensure MCP is configured:
Claude Code CLI:
bash
claude mcp add --transport http linear https://mcp.linear.app/mcp
Or add to settings.local.json:
json
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]
}
}
}
Authentication uses OAuth 2.1 - you'll be prompted to authorize on first use.
To clear cached auth: rm -rf ~/.mcp-auth
Examples
Tickets
- •"write a ticket for the auth bug we discussed" → activates write-ticket with bug template
- •"help me triage these 5 issues" → activates batch-review
- •"create a feature ticket for dark mode" → activates write-ticket with feature template
- •"what's the priority for this?" → activates triage workflow
Roadmap & Projects
- •"create a project for Q1 auth improvements" → activates manage-project
- •"how's the roadmap looking?" → activates roadmap-review
- •"what projects are at risk?" → activates roadmap-review with filter
- •"let's plan out the mobile app launch" → activates plan-initiative
- •"break this feature into a project with tickets" → activates plan-initiative
Starting Work
- •"let's start working on RAI-270" → activates start-work, creates branch
- •"create a branch for the auth feature" → creates ticket first, then branch
- •"start implementing the login fix" → activates start-work workflow
- •"I want to work on adding dark mode" → creates ticket + branch together
Workspace
- •"sync linear workspace" → refreshes workspace config
- •"refresh linear labels" → triggers workspace sync