linear-setuplisted

# Linear Setup You have a lot of repos and one brain. This skill sets up Linear so it doesn't fight you. The approach: **one team, one label group, custom views.** Not because it's the only way — because it's the right starting point for someone shipping across many projects without a big org chart. ## The philosophy Linear's concepts don't map 1:1 to how a solo dev with many repos works: | Linear concept | What it actually is | What you might assume | |---|---|---| | **Team** | Group of people with shared workflow | A repo or product | | **Project** | Time-bound feature/initiative | A repo or product | | **Label** | Flexible tag | — | | **Custom View** | Saved filter | — | The fix: use **one team** as your workspace, a **"Product" label group** to tag which repo/product each issue belongs to, and **custom views** filtered by label to get per-product boards when you need them. ## When to run this - First time setting up Linear for multi-repo work - Adding a batch of new repos to an existing setup - Reorganizing after things got messy - Someone asks "how should I organize Linear?" ## Step 1: Discover the workspace ```bash linctl whoami linctl team list --json linctl label list --team <TEAM_KEY> --json ``` Understand what's already there. If there's already one team — great, use it. If there are multiple teams, ask whether they want to consolidate or keep the structure. ## Step 2: Discover repos If the user works in a GitHub org, discover their repos: ```bash gh r