Smithery is now a part of Arcade.dev! Read more in our announcement here
Project and cycle management workflows with Linear. Use when implementing sprint planning, managing projects and roadmaps, or organizing work into cycles. Trigger with phrases like "linear project",...
Map planning intent onto the workspace's actual project, cycle, initiative, and team model before making relationship changes.
Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables.
nodes is complete.includeArchived: true when reconciliation needs them.Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <API_KEY>; OAuth tokens use Authorization: Bearer <ACCESS_TOKEN>. Store credentials server-side in an approved secret manager.
Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions.
Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
| Condition | Response |
|---|---|
| Ambiguous name match | Require a stable ID or owner-confirmed mapping. |
| Archived entity missing | Repeat the read with includeArchived: true before creating a replacement. |
| Cross-team access gap | Stop; do not infer visibility from project membership. |
| Partial batch | Record successful IDs, halt remaining writes, and reconcile before retrying. |
Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.
Input:
initiative=Q4; project=Billing; teams=ENG,PLAT; mode=dry-run
Expected handoff:
mapping=reviewed; visibility=pass; mutations=0; approval=pending
