Linear Planning

Turn project descriptions, feature requests, or codebases into well-structured Linear issues that agents can pick up and implement without ambiguity. Linear acts as the agent control plane — replacing markdown task files with a proper board with status tracking, dependency management, and team visibility.

Prerequisites: Official Linear MCP Server

Linear provides an official hosted MCP server — no npm package to install.

Claude Code setup (one command):

claude mcp add --transport http linear-server https://mcp.linear.app/mcp

Then run /mcp to complete OAuth authentication.

After connecting, run /mcp to see all available tools — the official server exposes tools for finding, creating, and updating issues, projects, and comments.

See references/mcp-setup.md for setup on other clients (Claude Desktop, Cursor, VS Code) and troubleshooting.

Important: Only the main Claude Code session can call MCP tools. Spawned subagents do not have MCP access. Subagents can help with Phase 1 codebase research (reading files, analyzing code), but all Linear MCP calls must happen in the main session.

The Core Principle: Tickets as Agent Briefs

Linear tickets in this workflow are complete work briefs for an AI agent, not status cards. A well-written ticket lets an agent pick it up and implement it without clarifying questions.

Every ticket must answer:

1. What — the specific deliverable
2. Why — context so the goal is clear
3. Where — exact files and directories
4. How — implementation approach or constraints
5. Done when — explicit, testable acceptance criteria

See references/issue-template.md for copy-paste templates.

Workflow: Research → Decompose → Approve → Create → Assign

Phase 1: Research

Gather all context needed to write good tickets. This phase is read-only — no Linear MCP calls yet.

Codebase research (can delegate to a subagent for file reading):

• Read CLAUDE.md, README, package.json for stack conventions
• Read relevant source files to understand existing architecture
• Identify files that will need changes

Linear context (main session only — MCP calls):

[teams tool]           → get teamId
[projects tool]        → get projectId for the team
[workflow states tool]  → get state IDs (Todo, In Progress, In Review, Done)
[labels tool]          → get label IDs if needed

Determine before proceeding:

• Which Linear team and project to use
• Whether there is an existing parent/epic to attach to
• The spec file path in the repo, if one exists
• The branch naming convention (e.g., feat/PROJ-123-short-title)

Phase 2: Decompose

Break the request into an epic + stories + tasks. Write the full draft — but DO NOT create anything in Linear yet.

Decomposition rules:

• Each issue must be completable in one agent session
• Minimize dependencies between issues
• Separate UI, API, and tests into distinct issues
• Blocked issues must explicitly reference their dependencies in the description
• Include priority and point estimates

Phase 3: Approval Gate

MANDATORY — Do not skip this phase. No Linear issues may be created until the user explicitly approves.

Present the full issue tree in a clear hierarchical format:

EPIC: [Title] [priority]
  STORY: [Title] [priority] [estimate]
    - AC: [acceptance criterion]
    - AC: [acceptance criterion]
  STORY: [Title] [priority] [estimate]
    - AC: [acceptance criterion]
    Blocked by: [dependency]
  STORY: [Title] [priority] [estimate]
    - AC: [acceptance criterion]

Example:

EPIC: Stripe billing integration [HIGH]
  STORY: Create billing UI components [HIGH] [3pts]
    - AC: PricingCard, BillingHistory, UpgradeModal render correctly
    - AC: Components use shadcn/ui and match design system
  STORY: Implement Stripe webhook handler [HIGH] [3pts]
    - AC: Webhook verifies signature and handles checkout.session.completed
    - AC: Subscription status syncs to database
  STORY: Add subscription creation API route [MEDIUM] [2pts]
    - AC: POST /api/billing/subscribe creates Stripe checkout session
    - AC: Returns checkout URL
  STORY: Write billing test suite [MEDIUM] [2pts]
    - AC: All API routes have Vitest tests
    - AC: Webhook handler tested with mock events
    Blocked by: webhook handler, subscription API

Then explicitly ask:

"Approve this plan, or tell me what to change."

WAIT for the user to respond. Do not proceed until you receive explicit approval.

Phase 4: Create Issues

Only after explicit user approval from Phase 3.

Create the parent issue (epic) first:

[create issue tool](
  teamId, projectId,
  title: "Stripe billing integration",
  description: """
  ## Overview
  [What this feature does and why]

  ## Spec
  See: docs/specs/billing.md

  ## Repo Context
  - Repo: ~/code/myapp
  - Framework: Next.js 15, Bun, Tailwind v4
  - Conventions: Biome linting, TypeScript strict, shadcn/ui

  ## Child Issues
  - [ ] Create billing UI components
  - [ ] Implement Stripe webhook handler
  - [ ] Write billing test suite
  """,
  priority: 2   # 1=urgent 2=high 3=medium 4=low
)

Then create child issues in order:

[create issue tool](
  teamId, projectId,
  parentId: "EPIC-ID",
  title: "Create billing UI components",
  description: "...",   # see issue-template.md for the full format
  stateId: "todo-state-id"
)

Each child issue description must include: context link to the parent, files to create/modify, implementation approach, and acceptance criteria.

Phase 5: Assign to Cycles (optional)

[active cycle tool](teamId)
[add to cycle tool](issueId, cycleId)

Agent Execution Loop

Include this pattern in every agent task description or spawn prompt so agents know the expected workflow:

1. Fetch issue details (read the full brief)
2. Read parent issue for project context
3. Update status -> "In Progress"
4. git checkout -b feat/PROJ-3-billing-ui-components
5. Implement the changes
6. bun run build && bun run lint
7. gh pr create --title "PROJ-3: Create billing UI components"
8. Update status -> "In Review"

Writing Great Ticket Descriptions

The biggest leverage point in this workflow is ticket quality. A vague ticket wastes the agent's context on clarification. A detailed ticket means straight implementation.

Bad:

Title: Fix billing page
Description: Something is broken on the billing page.

Good:

Title: Fix invoice download returning 404
Description:
## Bug
Download button on BillingHistory shows 404.
Root cause: URL uses /api/invoice/:id but route is /api/invoices/:id (plural).

## Files
- app/api/invoices/[id]/route.ts — correct route handler
- src/components/billing/BillingHistory.tsx:47 — where URL is built

## Fix
Line 47: `/api/invoice/${id}` -> `/api/invoices/${id}`

## Acceptance Criteria
- [ ] Download button fetches PDF without error
- [ ] bun run build passes

See references/issue-template.md for complete templates (feature, bug, refactor, epic).

References

• references/mcp-setup.md — Installing the official Linear MCP server, authentication, troubleshooting
• references/issue-template.md — Copy-paste templates for agent-ready tickets