How do I install the Linear Setup skill?

Run npx skillmds@latest add tjcages/linear-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Linear Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linear Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Linear Setup free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Linear Setup?

tjcages (@tjcages) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Linear Setup by tjcages — Agent Skill

Name: Linear Setup
Author: tjcages

Linear Setup

Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear tracking, track this project in Linear, add this repo to Linear, backfill history, get ready to track, or consents after a soft-nudge from linear-discipline. Anchors to North Star, backfills Done with evidence, wires blockedBy, installs per-repo discipline. NOT for one-off issue create/comment — Linear MCP handles that.

tjcages 29b9732 7 files · 70.1 KB Updated Sep 17, 2026

File contents

Linear setup

Chat rules: RESPONSE.md. Auth: AUTH.md. Full method: METHODOLOGY.md.

Step 0 — auth

Probe Linear MCP. On failure → AUTH.md steps for this agent; stop. Never invent API calls.

Operating order

Follow in sequence. Early gates exist because getting them wrong corrupts live workflows.

1. Already tracked? (§1a)

Search Linear by repo name and ask the user. Never assume blank slate.

Nothing → fresh bootstrap; continue.
Exists → STOP. Enumerate issues/milestones/labels/docs/status updates → summarize → per-category yes/no before any write. Extend conservatively. Scan repo for unmirrored roadmap docs (§4.7).

2. North Star (§1b)

README-as-vision is usually enough — say the call out loud. Question 5 (why track?) picks the shape — see METHODOLOGY goal→shape table.

3–4. Type + structure (§2–§3)

Suggested types: Product / Tool / Drop / Marketing. Milestones 1:1 with real phases. Separate engineering / launch / rollout tracks. Dates only with a real signal. Prefer §17 if shape is unclear.

5. Backfill (§4)

CHANGELOG > roadmap > git log. Feature-level default; per-release for launched packages. Done only with evidence. Doc “done” ≠ proof — corroborate (§4.8).

Writing (tickets)

Titles ≤8 words. Descriptions ≤3 sentences or ≤5 bullets. Comments ≤3 lines. Screenshots over prose (§10).

6. Wire (§4, §10, §11)

Real blockedBy/blocks. Surface UI-only items early (§11). Add README as Linear project document.

7. Install discipline (§5)

Write the tracking protocol into always-loaded agent instructions (CLAUDE.md / AGENTS.md / .cursor/rules/) with real team/project/milestone names. Bootstrap is not done without this.

8. Honesty (§6, §9)

Status updates at milestone/health moments only. atRisk before dates slip.

9. Done check (§18, §26)

Rubric ≥16/20 with no load-bearing 0, or full §26 audit.

After setup

Point user to always-on (if missing) via finish linear-tracking install. Optional Cursor weekly health: AUTOMATION.md. One next action.

---name: linear-setupdescription: Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear tracking, track this project in Linear, add this repo to Linear, backfill history, get ready to track, or consents after a soft-nudge from linear-discipline. Anchors to North Star, backfills Done with evidence, wires blockedBy, installs per-repo discipline. NOT for one-off issue create/comment — Linear MCP handles that.license: MIT---# Linear setupChat rules: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Full method: [METHODOLOGY.md](./METHODOLOGY.md).## Step 0 — authProbe Linear MCP. On failure → AUTH.md steps for this agent; **stop**. Never invent API calls.## Operating orderFollow **in sequence**. Early gates exist because getting them wrong corrupts live workflows.### 1. Already tracked? (§1a)Search Linear by repo name **and** ask the user. Never assume blank slate.- **Nothing** → fresh bootstrap; continue.- **Exists** → STOP. Enumerate issues/milestones/labels/docs/status updates → summarize → per-category yes/no **before any write**. Extend conservatively. Scan repo for unmirrored roadmap docs (§4.7).### 2. North Star (§1b)README-as-vision is usually enough — say the call out loud. Question 5 (why track?) picks the shape — see METHODOLOGY goal→shape table.### 3–4. Type + structure (§2–§3)Suggested types: Product / Tool / Drop / Marketing. Milestones 1:1 with real phases. Separate engineering / launch / rollout tracks. Dates only with a real signal. Prefer §17 if shape is unclear.### 5. Backfill (§4)CHANGELOG > roadmap > git log. Feature-level default; per-release for launched packages. Done only with evidence. Doc “done” ≠ proof — corroborate (§4.8).### Writing (tickets)Titles ≤8 words. Descriptions ≤3 sentences or ≤5 bullets. Comments ≤3 lines. Screenshots over prose (§10).### 6. Wire (§4, §10, §11)Real `blockedBy`/`blocks`. Surface UI-only items early (§11). Add README as Linear project document.### 7. Install discipline (§5)Write the tracking protocol into always-loaded agent instructions (`CLAUDE.md` / `AGENTS.md` / `.cursor/rules/`) with real team/project/milestone names. Bootstrap is not done without this.### 8. Honesty (§6, §9)Status updates at milestone/health moments only. `atRisk` before dates slip.### 9. Done check (§18, §26)Rubric ≥16/20 with no load-bearing 0, or full §26 audit.## After setupPoint user to always-on (if missing) via `finish linear-tracking install`. Optional Cursor weekly health: [AUTOMATION.md](./AUTOMATION.md). One next action.

Frequently asked questions