linear

name	linear
description	Use when the user wants to read, create, triage, or update issues, projects, labels, cycles, or team workflows in Linear; use the current host's Linear connector or MCP integration, read first for context, then batch the writes.

Linear

Intent

• Use for Linear issue triage, project updates, sprint planning, workload review, and documentation-linked follow-up work.

Default operating pattern

1. Confirm the workspace scope first: team, project, cycle, assignee, labels, or issue identifiers.
2. Use the current host's Linear connector or MCP integration to read context before making changes.
3. Group related reads together, then batch related writes together so the user can understand the change set.
4. For create or update flows, make the target state explicit: status, priority, owner, due date, labels, and linked issues or projects.
5. End with a concise handoff: what changed, what still needs confirmation, and the next likely Linear action.

Pack fit

• Included in: knowledge-ops
• Keep requests reusable across product, engineering, and operations workflows.

Boundary

• Do not update issues, projects, or labels before the target team or project is clear.
• Do not pretend a write succeeded without tool output confirming the mutation.