borghei/Claude-Skills / project-management/linear-expert
linear-expert
VerifiedAdministers Linear teams, cycles, projects and triage, and writes GraphQL API calls. Use when setting up or fixing a Linear workspace, scripting bulk changes, or migrating from Jira to Linear.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| assets/linear-team-template.md | markdown | 4.1 KB |
| assets/linear-triage-workflow.md | markdown | 5.2 KB |
| examples/jira-to-linear-migration.md | markdown | 11.7 KB |
| references/linear-concepts-and-workflows.md | markdown | 10.4 KB |
| references/linear-graphql-patterns.md | markdown | 12.9 KB |
| references/linear-vs-jira.md | markdown | 8.3 KB |
| references/red-flags.md | markdown | 13.1 KB |
assets/linear-team-template.md
View on GitHub# Linear Team Configuration Template
Copy this checklist when creating a new Linear team. Adjust the bracketed values; defaults reflect what works for a 5-15 person product engineering team shipping a SaaS product.
---
## 1. Team Identity
- **Team name:** `[Engineering]`
- **Team key:** `[ENG]` (2-4 uppercase letters; immutable; prefixes every issue ID)
- **Team icon and color:** pick something distinct from other teams
- **Description:** one sentence on the team's mission
## 2. Cycles
- **Cycles enabled:** Yes (set No only for support/triage-only teams)
- **Cycle duration:** `[2 weeks]`
- **Cycle starts on:** `[Monday]`
- **Auto-archive completed cycles after:** `[6 cycles]`
- **Upcoming cycles to show:** `[3]`
## 3. Triage
- **Triage enabled:** Yes (almost always; the inbox for inbound issues)
- **Triage responsibility:** rotation, one person per day or per cycle
- **Auto-assign new issues to triage when:** created via integration, API, or by a non-team-member
## 4. Estimation
- **Scale:** `[Fibonacci]` (0, 1, 2, 3, 5, 8) — closest analog to Jira story points
- **Allow zero estimate:** Yes (use for genuinely trivial work)
- **Enforce estimates before issues enter a cycle:** Yes (team norm; not auto-enforced)
## 5. Workflow States
Use the default 6-state workflow unless there is a specific need:
| Type | State Name | Notes |
|---|---|---|
| `triage` | Triage | Inbox for unrouted issues |
| `backlog` | Backlog | Future work, not yet committed |
| `unstarted` | Todo | Committed to a cycle but not started |
| `started` | In Progress | Active work |
| `started` | In Review | PR open / awaiting QA |
| `completed` | Done | Shipped / closed as done |
| `canceled` | Canceled | Won't do, duplicate, obsolete |
Resist adding more states; use labels for nuance (e.g. `status/blocked`, `status/awaiting-customer`).
## 6. Labels (recommended starter set)
### Type label group (mutually exclusive)
- `type/feature`
- `type/bug`
- `type/chore`
- `type/spike`
- `type/incident`
### Area label group (mutually exclusive)
- `area/api`
- `area/web`
- `area/mobile`
- `area/infra`
- `area/data`
### Free-form labels
- `tech-debt`
- `customer-request`
- `security`
- `breaking-change`
- `good-first-issue`
## 7. Members and Permissions
- **Team admins:** 2 (the team lead + one backup)
- **Members:** every IC and manager on the team
- **Guests:** designers, PMs, support engineers who file issues but do not own delivery
## 8. Integrations
- **GitHub:** install Linear GitHub app; connect the team's primary repos.
- **Slack:** route Initiative updates and Project status updates to `#team-[name]-updates`.
- **PagerDuty / on-call:** if applicable, auto-create incidents as Linear issues with `type/incident`.
- **Figma:** enable the Figma integration so attached frames render inline.
## 9. Templates
Create 3-5 issue templates the team will actually use:
- **Bug report** — sections for repro, expected, actual, environment.
- **Feature request** — problem, proposed solution, success criteria.
- **Spike** — question, time-box, acceptance criteria for the writeup.
- **Incident** — timeline, impact, root cause, follow-ups (link to postmortem).
- **Tech-debt** — debt description, cost of inaction, proposed fix.
## 10. Cadences
| Ceremony | Frequency | Owner |
|---|---|---|
| Cycle planning | Monday of cycle start | Team lead |
| Cycle review | Friday before cycle end | Team lead |
| Triage rotation | Daily, ~15 min | Rotating |
| Initiative update | Weekly | Initiative owner |
| Project status update | Weekly | Project lead |
## 11. Conventions Document
Pin a Linear issue titled "Team conventions" with:
- This template, filled in.
- Branch naming convention (`<user>/eng-<number>-<slug>`).
- PR magic words (`Fixes ENG-123`).
- Estimation rubric (what does a 3 mean vs a 5?).
- Definition of done.
## 12. Audit Schedule
- **Quarterly:** review labels (merge unused, retire stale).
- **Quarterly:** review templates (are they being used? still relevant?).
- **Quarterly:** review automations and integrations.
- **Annually:** review workflow states (is the team still happy with the shape?).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |