Skip to content

`linear` — guides

Understand the boundary between first-time repository intake and approval-gated synchronization of an existing brief.

Mode: tracker-authoritative. These guides assume Linear holds the team’s real backlog. If docs/product/ is canonical and Linear is only for reporting, choose repo-first projection below.

Linear integration for this catalogue. Read Linear work into the shared content-based repository route, or compare an existing tracker-origin artifact through a separate approval-gated refresh workflow.

The API key never reaches the model. linear is a credentialed skill: it invokes a CLI that resolves your Personal API Key in-process and makes the GraphQL call itself.

Begin the interactive setup with:

Set up credentials for Linear so I can read the Checkout Redesign project into this repository.

Repo-first projection (the product-shaping default): Use this when product shaping happens in docs/product/ and Linear is a shallow copy for reporting and team visibility. Feature intents and slices are projected out; the intent tree stays canonical, status never returns from Linear, and the projection contract is applied by hand or through a one-shot export you operate; no exporter or live API integration ships today.

Tracker-authoritative: Use this when Linear holds the team’s real backlog. Intake reads that work into the repository without changing Linear. Reviewed refresh can add only a comment, display status, trace link, pull-request link, or closure after separate confirmation; it cannot create an issue or rewrite a requirement body.

Do not mix the modes. Requirements edited in two places diverge silently.

New here? Generate a Personal API Key at Linear → Settings → API → Personal API keys, then run credential-setup to store it. Then read Choose Linear intake or brief sync to decide where to start.

Task-oriented recipes for a problem you already have.


The two-layer credential model — why the skill never holds your token — lives with the credential-brokers pack. Installing and upgrading the catalogue live in ../_shared/.