# Soloscrum Tracker Linear Add Dependency

> Operation: declare a blocking relation between Linear issues using Blocks/Blocked by. Used when active tracker profile is linear+github.

- Skill: `mew-ton/soloscrum-tracker-linear-add-dependency` (Agent Skill)
- Install (CLI): `npx get-skill add mew-ton/soloscrum-tracker-linear-add-dependency`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mew-ton/soloscrum-tracker-linear-add-dependency/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mew-ton (https://skillmd.com/u/mew-ton)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/mew-ton/soloscrum-tracker-linear-add-dependency

---


# soloscrum-tracker-linear-add-dependency

Declares a blocking relation between two Linear issues. Active when `tracker_profile = linear+github`.

## Inputs

- `linear_id` — Linear issue that depends on others (the dependent)
- `depends_on` — list of Linear IDs it depends on

## Steps

1. For each `<dep>` in `depends_on`, create a relation:
   - Linear MCP — `save_issue` with `id = <linear_id>`, `relationsToAdd = [{ relatedIssueId: "<dep>", type: "blocked_by" }]`
   - The valid `IssueRelationType` enum values are `blocks` / `blocked_by` / `related` / `duplicate` / `duplicate_of` (snake_case)

## Output

- Confirmation that all blocking relations are recorded

## Notes

- Linear's native UI surfaces "Blocked by" prominently — no extra body editing needed
- Parent–child decomposition uses `parentId` (handled by `soloscrum-tracker-linear-create-subtask`); this operation is for **peer blocking** only
- The reverse relation (`blocks`) is auto-created by Linear on the other side

