Manage Linear

Linear Integration

Use the linear-cc CLI tool for all Linear operations. All commands return JSON.

Shared reference: See _shared/linear-integration/ for:

• CLI reference - Canonical commands
• Status milestones - When to change status
• Comment templates - Structured formats
• Error handling - Warn and continue pattern

Commands

Create Issue

npx tsx .claude/tools/linear-cc/src/index.ts create-issue "Issue title" \
  --label feature \
  --project "Project Name" \
  --description "Description text"

Required: title, --project (enforced by workflow) Optional: --label, --assignee, --unassigned, --description, --priority (1-4)

Auto-assignment: Issues are automatically assigned to the current user unless:

• --assignee "Name" → assigns to specified person
• --unassigned → leaves issue unassigned

Get Issue

npx tsx .claude/tools/linear-cc/src/index.ts get-issue DIS-47

Update Status

npx tsx .claude/tools/linear-cc/src/index.ts update-status DIS-47 in-progress

Valid statuses: backlog, todo, in-progress, in-review, done, canceled

Update Issue

npx tsx .claude/tools/linear-cc/src/index.ts update-issue DIS-47 \
  --description "Updated description text" \
  --project "Project Name" \
  --assignee "Andy Rong" \
  --priority 2

Optional: --description, --project, --assignee, --priority (1-4), --due (YYYY-MM-DD)

Create Comment

npx tsx .claude/tools/linear-cc/src/index.ts create-comment DIS-47 "Comment body"

Create Document

npx tsx .claude/tools/linear-cc/src/index.ts create-document "Document Title" "Content here" \
  --issue PRO-123

Required: title Optional: content, --file <path>, --issue <id>, --project <uuid>

Creates a document attached to an issue or project. Preferred over comments for:

• Checkpoint handoffs (editable, searchable)
• Long-form context that may need updates
• Documentation that should be visible under Resources tab

List Issues

npx tsx .claude/tools/linear-cc/src/index.ts list-issues --status in-progress --label feature

Optional: --status, --label, --project, --assignee, --limit

List Projects

npx tsx .claude/tools/linear-cc/src/index.ts list-projects

Lists all available projects from cache. Used during issue creation to prompt for project selection.

Create Project

npx tsx .claude/tools/linear-cc/src/index.ts create-project "Project Name" \
  --description "Project description"

Required: name Optional: --description

Sync (Setup)

npx tsx .claude/tools/linear-cc/src/index.ts sync

Run this once to cache team IDs. Required before other commands.

Spec Writing Workflow

REQUIRED: Before creating any issue, write a proper spec.

Quick Issues (skip spec)

Skip the full spec process if ALL are true:

• Single file change
• < 20 lines of code
• No UI/UX decisions
• No architectural decisions

Standard Issues (full spec required)

For features, improvements, or UI work:

1. Gather requirements using question-bank.md
2. Write spec following spec-template.md
3. Create issue with spec as description

Spec Checklist

Verify before creating issue:

• Problem statement explains WHY
• User story identifies WHO and WHAT
• Acceptance criteria are testable
• Edge cases covered (if applicable)

Executing Specs

When starting work on a spec:

1. Convert acceptance criteria to TodoWrite items
2. Mark todos as in_progress/completed as you work
3. Post progress updates to Linear via create-comment

Response Format

Success:

{"success": true, "identifier": "DIS-47", "url": "https://linear.app/..."}

Error:

{"success": false, "error": "Error message"}

Available Options

Labels

bug, feature, improvement, spec, ui, ux, refactor, tests, documentation, ci/cd, bug-fix, ui/ux

Projects

Nebula, DX Improvements, Code Quality Agents, Claude Code Skills, Global Features, Design Studio, Settings, Website and Marketing, Home Dashboard, Deals Board, Investors Tab, Property Data Aggregation - Phase 1, Prototype Enhancements, v2 Dispo Genius, Project Blue

Members

Andy Rong, zeeshan@dispogenius.io, ali@dispogenius.io, arbaz@dispogenius.io

Statuses

backlog, todo, in-progress, in-review, done, canceled, duplicate

Usage Pattern

1. User asks to create/manage Linear issues
2. Run the appropriate CLI command
3. Parse JSON response
4. Report result to user

Example: User: "Create a test issue in Prototype Enhancements" → Run: npx tsx .claude/tools/linear-cc/src/index.ts create-issue "Test issue" --project "Prototype Enhancements" → Response: {"success": true, "identifier": "DIS-150", "url": "..."} → Report: "Created DIS-150: https://linear.app/..."