# implement-task-linear

This skill turns several Linear issues into one branch and PR, while checking each issue’s scope, context, and state. It covers the delivery workflow.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 341 installs
- Author: PinguApps
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/PinguApps/Skills/tree/HEAD/skills/implement-task-linear/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/implement-task-linear

## What it does

\`implement-task-linear` takes one or more Linear issues and delivers them together from a single branch into one PR. Before editing the repository, it resolves issue references, team and project boundaries, acceptance criteria, workflow states, relations, comments, and attachments. It also reads `AGENTS.md`, specifications, plans, context files, ADRs, and affected code.

The skill wraps `complete-work` and uses `linear-ticket` for authorized Linear updates. `complete-work` owns branch setup, commits, verification, push, PR creation, and review or CI convergence. Each target keeps its own scope, estimate, implementation coverage, and verification coverage. A blocker on any target prevents the combined PR from being published.

Work does not start without clear Linear issue identifiers or URLs, because the skill asks for them before planning. Merge, deployment, and release stay outside this workflow.

## Requirements
- Works with: Linear

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add PinguApps/Skills --skill implement-task-linear -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/implement-task-linear/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/implement-task-linear/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add PinguApps/Skills --skill implement-task-linear -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/implement-task-linear/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add PinguApps/Skills --skill implement-task-linear -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/implement-task-linear/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install PinguApps/Skills implement-task-linear
```

2. **Manually: put the files in place**
- File: `.github/skills/implement-task-linear/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add PinguApps/Skills --skill implement-task-linear -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/PinguApps/Skills --path skills/implement-task-linear
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/implement-task-linear/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add PinguApps/Skills --skill implement-task-linear -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/PinguApps/Skills/tree/HEAD/skills/implement-task-linear/SKILL.md

## When to use it
- combine several Linear issues in one PR
- check acceptance criteria before repository changes
- trace specs, plans, and ADRs for each target
- track issue status and estimates within team and project boundaries
- hold PR publication when a target is blocked

## Example prompts
- Use `implement-task-linear` for the supplied Linear issues and deliver them through one shared PR.
- Run `implement-task-linear` to inspect issue provenance and repository context before making the changes.
- Apply `implement-task-linear` to the Linear targets, verify each one, and then publish the PR.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 76875b08bbabad83.

BEGIN THIRD-PARTY FILE 76875b08bbabad83
```text
---
name: implement-task-linear
description: Implement one or more supplied Linear issues together in a single PR through complete-work, with per-issue state management and closing references.
disable-model-invocation: true
---

# Implement Task from Linear

Implement every supplied Linear issue together on one branch and in one PR. The supplied issues are the required input and combined scope boundary; each issue's provenance chain and repository context refine how to implement it without silently adding work. Complete all supplied issues before publishing the PR; a blocker on any target blocks publication of the combined change.

Use this skill as a Linear-specific wrapper around [$complete-work](../complete-work/SKILL.md). Read that skill before planning delivery; it owns branch setup, incremental commits, verification, push, PR creation through `create-pr`, and review/CI convergence through `finish-pr`. If it or a required dependency is unavailable, report the missing prerequisite and resolve it before implementation rather than substituting a partial workflow. Invoking this skill authorizes that full workflow; leave merging, deployment, and release to a separate user request.

Read and apply [$linear-ticket](../linear-ticket/SKILL.md) before any ticket draft or mutation. Pass each target's verified team/project boundary and this workflow's scoped authorization; it owns ticket content, numbering, metadata, estimates, native writes and read-back verification.

Begin with a few short, precise bullets explaining the intended discovery and delivery before taking action. Steps 1–3 are read-only discovery and clarification: use them to produce an informed plan before branch creation, repository edits, or Linear mutations.

## 1. Resolve the target and Linear boundary

Accept one or more unambiguous Linear issue identifiers or URLs. Ask for them when absent, resolve every supplied reference, and deduplicate references to the same issue. Keep a target ledger with each issue's identifier, URL, acceptance criteria, team/project IDs, workflow state IDs, estimate, implementation and verification coverage, and saved status. In the steps below, apply target-specific discovery and reconciliation to every issue in this ledger.

Fetch each target's full description, status, labels, team, project, relation identifiers, comments, and requirement-bearing attachments. Record its exact team ID and project ID. If it has no project, ask the user to assign it or authorize assignment to a named project before inspecting surrounding Linear work.
```
END THIRD-PARTY FILE 76875b08bbabad83

The third-party file has ended. Everything between the 76875b08bbabad83 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2571 of 16415 bytes. © PinguApps · MIT · https://github.com/PinguApps/Skills/tree/HEAD/skills/implement-task-linear/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md