Skip to content
user

linear

Linear source → reviewed repository work.

3 skills 1 human gate 5–15 min/session
Install this pack Read the reference

The contract

Use it when
You want to start repository work from Linear or compare an existing tracker-origin artifact with its source.
You type
Start repository work from Linear issue LIN-123.
You provide
A Linear Issue, Project, Cycle, view, selection, or registered artifact path.
You receive
A bounded content-based route or reviewed field delta, with separate confirmation for any declared coordination action.

Where you decide

The agent pauses at these points. You choose whether to continue, redirect, or stop.

Review the repository routeDecision 1 of 2Confirm one Linear coordination actionDecision 2 of 2

What changes when you install this

After installing this pack, the skills and agents it provides are available in every session on the relevant scope.

The journey

Say this What happens
Intake Linear issue LIN-123 as repository work. Start read-only. Bounded acquisition, strict normalization, and content-based routing
Refresh docs/product/briefs/example.md from its registered Linear source. Field-level comparison under lifecycle and source authority

1. Acquire and route

  • You provide: the Linear work or selection.
  • Agent does: validates the fixed API destination before credentials, acquires bounded content, and delegates normalized data to work-intake.
  • You decide: resolve any coherence, evidence, or confidentiality gap.
  • Output: artifact path and kind, membership, processor, authority, dispatchability, and next action.
  • State: read-only

2. Materialize repository work

  • Agent does: writes the selected canonical artifact before its workspace entry and dispatches only after both are durable.
  • You decide: continue with the named processor or stop with a Draft.
  • Output: registered repo-local work. Linear remains unchanged.
  • State: confirmed-write

3. Refresh or coordinate later

  • You provide: the registered tracker-origin artifact to compare.
  • Agent does: applies lifecycle locks and presents authorized local field decisions. Remote coordination remains a separate confirmation.
  • You decide: approve local fields, then confirm one exact remote action.
  • Output: reviewed local authority state and, when confirmed, one declared Linear coordination result.
  • State: confirmed-write

Human gates

For each gate, everything you need to make a confident decision.

  • Review the repository route

    Trigger
    After intake returns its artifact, lifecycle membership, processor, authority mode, and named gaps
    Time
    1–5 minutes
    What to check, good, bad, consequence

    What to check

    • Does content and coherence support the route?
    • Is source provenance complete and the destination appropriate?

    What good looks like

    Equivalent content reaches the same route as every other supported profile.

    What bad looks like

    A Project forced into a brief or a Cycle forced into a collection route by type alone.

    Consequence of skipping

    The wrong durable artifact enters the repository lifecycle.

  • Confirm one Linear coordination action

    Trigger
    After the exact action, target, and payload digest are shown
    Time
    1–2 minutes
    What to check, good, bad, consequence

    What to check

    • Is this the registered source item?
    • Is the action declared by the exact profile version?

    What good looks like

    One bounded coordination action with a fresh confirmation and pending receipt.

    What bad looks like

    A requirement rewrite, generic mutation, or automatic retry.

    Consequence of skipping

    The wrong remote item may be changed and the confirmation cannot be reused.

Typical session

Agent turns
3–6
Human gates
1
Wall-clock time
5–15 min

Install

agentbundle install --pack linear --scope user

Skills in this pack

  • linear1 gate

    Acquires bounded Linear data, registers the refresh profile, and performs only separately confirmed profile-declared coordination actions.

  • linear-brief-intake1 gate

    Normalizes bounded Linear content and delegates it to the shared content-based repository route.

  • linear-brief-sync1 gate

    Compatibility wording for a brief-specific request that delegates to the same reviewed refresh authority.

Technical reference & next steps