Analyze Linear workspace health and usage patterns before jumping into backlog work. Like a pre-flight check for a new PM joining a team or organization.
/plugin marketplace add breethomas/pm-thought-partner/plugin install breethomas-pm-thought-partner@breethomas/pm-thought-partnerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/health-indicators.mdreferences/linear-methodology.mdAnalyze Linear workspace health and usage patterns before jumping into backlog work. Like a pre-flight check for a new PM joining a team or organization.
Auto-invoke this skill when:
/lno-prioritize on an unfamiliar workspaceTrigger phrases:
Gather data about the workspace structure using Linear MCP tools:
Compare reality to Linear's methodology (see references/linear-methodology.md):
Produce actionable output:
I'll analyze this Linear workspace to help you understand:
- How it's structured (teams, projects, workflows)
- What's healthy vs concerning
- How this org uses Linear compared to best practices
- Where to focus your attention
This takes a few minutes. I'll pull data across teams and issues.
Use Linear MCP tools to collect:
1. Teams
- list_teams: Get all teams
- For each active team: get_team for details
- Note: member count, activity, naming patterns
2. Issues (sample)
- list_issues with various filters:
- Recent issues (last 30 days)
- Stale issues (no update in 90 days)
- Sample from multiple teams
- Analyze: titles, descriptions, age distribution
3. Projects
- list_projects: Get all projects
- Note: leads, dates, status, issue counts
4. Cycles (if used)
- list_cycles for active teams
- Note: completion rates, carryover
5. Labels
- list_issue_labels: Get all labels
- Note: count, naming consistency, usage
6. Statuses
- list_issue_statuses for key teams
- Note: complexity, customization
For each dimension, compare findings to Linear best practices:
Team Structure:
Issue Quality:
Backlog Health:
Project Health:
Workflow Complexity:
Use this format:
# Workspace Calibration Report
**Workspace:** [name]
**Date:** [date]
**Analyzed:** [X teams, Y issues sampled, Z projects]
---
## Executive Summary
[2-3 sentences: Overall health, key findings, top concerns]
---
## Health Indicators
| Dimension | Status | Finding |
|-----------|--------|---------|
| Team Structure | 🟢/🟡/🔴 | [summary] |
| Issue Quality | 🟢/🟡/🔴 | [summary] |
| Backlog Health | 🟢/🟡/🔴 | [summary] |
| Project Health | 🟢/🟡/🔴 | [summary] |
| Cycle Usage | 🟢/🟡/🔴 | [summary] |
| Workflow Complexity | 🟢/🟡/🔴 | [summary] |
| Triage Usage | 🟢/🟡/🔴 | [summary] |
| Label Hygiene | 🟢/🟡/🔴 | [summary] |
---
## How This Org Uses Linear
[Describe the patterns observed - team structure philosophy,
workflow conventions, project usage, cycle rhythm, etc.
This helps a new PM understand "how we do things here."]
### Teams
[List key teams with brief description of what they own]
### Conventions
- Issue titles: [pattern observed]
- Labels: [how they're used]
- Projects: [how they're scoped]
- Cycles: [if/how they're used]
---
## Red Flags
[List specific issues requiring attention]
1. **[Issue]**: [Details and why it matters]
2. **[Issue]**: [Details and why it matters]
---
## Recommendations
### Immediate (This Week)
1. [Specific action]
2. [Specific action]
### Near-Term (This Month)
1. [Specific action]
2. [Specific action]
### Consider (When Ready)
1. [Larger improvement]
---
## Gut-Check Questions
Before diving into backlog work, consider:
- [ ] Can you explain what each team owns in one sentence?
- [ ] Do you know where to file any given issue within 2 clicks?
- [ ] Are there teams that should be consolidated?
- [ ] Is there stale work that should be archived?
---
*Calibration powered by PM Thought Partner*
*Methodology: Linear Method (linear.app/method)*
Your workspace is calibrated. Here's what I'd suggest:
1. [If red flags]: Address the [specific issue] first
2. [If healthy]: You're ready to run /lno-prioritize on [team]
3. [If context needed]: Want me to deep-dive on any dimension?
I now have context about how this org uses Linear. Future backlog
commands will account for your workspace patterns.
Linear's methodology is opinionated. Some orgs intentionally deviate. The goal is:
This skill is especially valuable for PMs joining an existing org:
Calibration provides context for subsequent commands:
/lno-prioritize works better when you understand team structure/four-risks makes more sense when you know project conventionsAfter calibration:
/lno-prioritize, /now-next-later: Run with understanding of conventionsIf Linear MCP isn't configured:
I'd like to analyze your Linear workspace, but I don't have access.
To enable workspace calibration:
1. Get a Linear API key (Settings > Account > Security & Access)
2. Ask Claude "Set up the Linear MCP server"
Alternatively, you can describe your workspace structure and I'll
help you think through it manually.
For workspaces with 50+ teams or 10K+ issues:
This is a large workspace. I'll sample strategically rather than
analyzing everything:
- All teams (for structure analysis)
- 100-200 issues across key teams (for quality patterns)
- Active projects only (for project health)
This gives representative data without overwhelming the analysis.
For new workspaces with minimal data:
This workspace is relatively new with limited history.
Instead of a full health check, I'll help you:
- Set up team structure following Linear best practices
- Establish conventions before patterns emerge
- Avoid common pitfalls (labels-as-teams, user story format, etc.)
references/linear-methodology.md - Linear's recommended practicesreferences/health-indicators.md - Detailed health dimensions and thresholdsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.