SkillsAdd

tjcages/linear · Archived

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.

First seen Jul 30, 2026

Installation

$ npx skills add tjcages/linear --skill linear-setup
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

linear-discipline Same source · more installs
tjcages/linear

>- Always-on Linear session discipline and one-time soft nudge for untracked repos. Use wheneve…

30 installs
linear-methodology Same source
tjcages/linear

>- Proven methodology for building and tracking features, projects, and issues in Linear. Use w…

27 installs
linear-sync Same source
tjcages/linear

>- Sync, audit, or rescue an existing Linear project against repo reality. Use when the user as…

25 installs
linear-monitor Same source
tjcages/linear

>- Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use w…

25 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

linear Similar name
openai/skills

Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or …

8.2K installs
linear-release-setup Similar name
linear/linear-release

Generate CI/CD configuration for Linear Release. Use when setting up release tracking, configur…

15K installs
orca-linear Similar name
stablyai/orca

>- Use Orca's Linear CLI through `orca linear ...` commands to read linked ticket context with …

11.3K installs
linear-cli Similar name
schpet/linear-cli

Manage Linear issues from the command line using the linear cli. This skill allows automating l…

7.8K installs
Linear Automation Similar name
claude-office-skills/skills

Automate Linear issue tracking, cycle planning, roadmap management, and engineering workflows

3.9K installs
linear Similar name
lobehub/lobehub

Linear issue management. Use for LOBE-xxx issues, Linear links, PRs referencing Linear, retriev…

3.8K installs

Also in this package

Other skills from tjcages/linear.

npx skills add tjcages/linear
linear-discipline 30 linear-methodology 27 linear-sync 25 linear-monitor 25 linear-finish-install 25

Browse all from tjcages/linear

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.2
Declared agents claude-code cursor

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,719 B
  • docs SUMMARY.md 472 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 27 installs

SKILL.md

Linear setup

Chat rules: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Full method: [METHODOLOGY.md](./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](./AUTOMATION.md). One next action.