Skip to main content
Linear is the primary tool for planning, tracking, and organizing engineering work at Ignition Labs.
This document defines how we use Linear in a calm, clear, and sustainable way.

​
1. Purpose of Linear

Linear complements our engineering process by providing:
  • A single source of truth for active work
  • A clean, structured view of priorities
  • A calm workflow that avoids confusion or overwhelm
  • Smooth integration with GitHub pull requests
We keep Linear simple.
No clutter. No unnecessary labels. No pressure.

​
2. Issue structure

Each Linear issue should include:
  • Clear title
  • Short summary (1–3 sentences)
  • Motivation (why it matters)
  • Acceptance criteria
  • Links to designs, PRs, or code references
Linear issues should be easy to scan and understand.

​
3. Labels & types

We use a minimal set of classifications:

​
Issue types

  • Feature: new functionality
  • Improvement: refinement to an existing feature
  • Bug: something broken or incorrect
  • Chore: cleanup, setup, refactoring, or maintenance
  • Research: exploration or spikes

​
Labels

Labels are intentionally few:
  • web
  • mobile
  • ingestion
  • ui
  • backend
More labels may be added as the company grows, but the system should remain uncluttered.

​
4. Sprints

Sprints represent focused 1–2 week periods of work in Linear. Sprint guidelines:
  • Small scope
  • Clear goals
  • No overloaded commitments
  • Issues may move to the next sprint without stress
Each sprint should feel achievable and predictable.

​
5. Projects

Projects are used only for:
  • Multi-step deliverables
  • Product features that span multiple sprints
  • System upgrades or migrations
  • Company-level initiatives
Projects help visualize progress without adding pressure.

​
6. Workflow

​
1. Create an issue

Created either directly in Linear or from a GitHub PR.
Use the issue template guidelines above.

​
2. Prioritize

Move issues into:
  • Backlog (not yet prioritized)
  • Later (planned but not urgent)
  • Next Sprint (upcoming work)

​
3. Work the current sprint

Active work lives in:
  • In Progress
  • In Review
  • Done

​
4. Connect PRs

Every PR in GitHub should link to its Linear issue.
Linear will automatically update the status as PRs open and merge.

​
7. Calm communication

Linear is not a place for stress.
Notes and comments should be:
  • Clear
  • Supportive
  • Helpful
  • Concise
Documentation lives in the repo; Linear holds the plan.

​
8. When to use GitHub instead

Use GitHub Issues for:
  • External or community-facing tasks
  • Public bug reports
  • Long-form documentation work
Linear remains internal and engineering-focused.

​
9. Final note

Linear exists to bring clarity to the engineering workflow, not pressure.
It’s a tool to help us move thoughtfully, maintain focus, and progress with confidence. At Ignition Labs, calm workflow leads to calm products.