Linear with Teamlead

Compose the two workflows without copying either one. Read the installed linear skill and the selected Teamlead skill before starting. The Linear skill owns identity, issue contracts, artifacts, comments, metadata, and status. The Teamlead skill owns execution, delegation, synthesis, verification, and review mechanics.

This bridge never grants coordination or delegation authority. An Orchestrator may load the orchestrator skill and coordinator flows. A terminal Explorer, Planner, Builder, or Reviewer loads only its matching terminal role skill and must not load Herdr or coordinator skills.

Use this bridge only when repository instructions opt into Linear and the work is tied to a real Linear issue. If either required skill is unavailable, name the missing dependency and stop the integrated workflow rather than guessing its contract.

Add tracker context at the boundary

Do not add Linear fields to generic Teamlead brief templates. When a role brief belongs to a Linear-backed phase, append only the integration context that role needs: