SpecBot

How to Write Better Linear Issues

Complete guide to writing high-quality Linear issues.

Issue Structure

Concise, descriptive title

Explain the what, why, and how

Clear criteria for completion

What needs to be done first

Time estimate for completion

Include specific details and examples

Avoid jargon and ambiguity

Split large issues into smaller, actionable ones

Provide all relevant background information

New functionality to be added

Issues that need to be fixed

Enhancements to existing features

Code improvements and refactoring

Maintenance and operational tasks

What's the most important part of a Linear issue?

The acceptance criteria. Without clear criteria, it's hard to know when the issue is done.

How do I estimate issues accurately?

Break the issue down into smaller tasks, estimate each task, and sum them up. Consider complexity, dependencies, and unknowns.