linear-method

# Linear Method

This skill embodies Linear's philosophy and best practices for building software with focus, momentum, and quality. Use it to help organize work according to proven principles that distinguish world-class product teams.

## Core Philosophy

**Speed through simplicity**: Tools should help creators stay productive, not create bureaucracy. Keep individuals moving fast rather than generating perfect reports.

**Momentum over perfection**: Take swift action daily. Ship constantly. Multiple small launches beat one big launch.

**Clarity of direction**: Connect every task to larger goals. Everyone should understand what matters and why.

**Manageable scope**: Scope projects down aggressively. Break large work into completable stages. Small, concrete tasks feel great to finish.

## Writing Issues (The Linear Way)

Issues communicate tasks clearly and concisely. NO user stories—they're cargo cult that wastes time.

### Issue Structure

**Title**: Plain language describing the task
```
Good: "Add password reset flow"
Bad: "As a user, I want to reset my password so that..."
```

**Description** (when needed):
- What needs to be done
- Why it matters (brief context)
- Acceptance criteria (if complex)
- Links to relevant user feedback (quote directly, don't summarize)

### Key Principles

1. **Write your own issues**: Forces deep thinking about the problem
2. **Describe tasks with clear outcomes**: Code, design, document, or action
3. **Keep it brief**: If it needs explanation, it's too big—break it down
4. **Quote user feedback directly**: Users describe pain authentically
5. **Everyone writes their own work**: The person doing the work understands it best

### What Makes a Good Issue

✅ **Good Issues**:
- "Implement email verification for signup"
- "Fix sidebar navigation on mobile (clips off screen)"
- "Add loading state to dashboard while fetching data"
- "Research best practices for rate limiting APIs"

❌ **Bad Issues** (User Stories):
- "As a user, I want