What is linear-scrum?

A connection between a dev-flow project and Linear, a project-management tool for tracking issues and work cycles. It applies agile Scrum, a method of planning work in short, fixed periods called sprints.

Use it to create or link a Linear project, turn a tasks.md file into labelled issues, set up two-week cycles, plan work against team velocity, and sync task changes.

It keeps project tasks, statuses, estimates, sprint planning, and progress in one shared tracking system instead of maintaining separate records.

linear-scrum — Skill by lukedj78

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/lukedj78/dev-flow/linear-scrum

Any agent

npx skills add lukedj78/dev-flow --skill linear-scrum

Clone the repo

git clone --depth 1 https://github.com/lukedj78/dev-flow

Made for: Claude Code, Codex.

Per session 185 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,732 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00185	$0.01732
Opus 5	$0.00093	$0.00866
Sonnet 5	$0.00037	$0.00346
Haiku 4.5	$0.00018	$0.00173

Measured 2d ago against content hash 19e78b2bd417, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linear-scrum scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/meta_linear.py, scripts/task_key.py, scripts/test_scripts.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

linear-scrum/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

linear-scrum — Linear integration + agile scrum for a dev-flow project

This skill owns the Linear side of a dev-flow project. It writes to Linear (via the connected Linear MCP) and to the linear / scrum blocks of .workflow/meta.json. It never touches app/, apps/agent/, or other framework files, and it does not change the phase enum — like eve-agent and the discipline skills it records state in meta.json and appends history, and is never a phase gate.

Read references/contracts.md for the .workflow/ contract, references/scrum-model.md for the scrum conventions, and references/linear-mcp.md for the exact Linear MCP operations.

Preconditions

A Linear MCP must be connected in the session. Confirm with list_teams before any write. For the headless server loop use the API-key path in docs/loop-engineering.md instead — this skill is the interactive counterpart.
.workflow/meta.json exists (dev-flow project). If not, tell the user and stop.
.workflow/tasks.md exists for Setup mode (run prd-to-tasks first otherwise). Coupled format: scripts/task_key.py derives its dedup key from the - [ ] **<Title>** — <body> line shape produced by prd-to-tasks, splitting on the em-dash (—) to isolate the title — if tasks.md was hand-edited to use a different separator, dedup breaks and Setup/Sync can create duplicate issues.

Read state, then pick a mode

Read .workflow/meta.json:

No meta.json#linear and tasks.md present → Setup mode.
A Linear Project already exists for this project but meta.json#linear is absent/partial → Adopt mode.
meta.json#linear present → Sync mode.

Do one logical operation per invocation, then stop. Every mode is idempotent.

Setup mode (new project)

list_teams → resolve the team (single team today: Lucadigerlando). One dev-flow project = one Linear Project under that team, never a new team.
Ensure scrum config on the team:
- Estimates — verified working: save_issue accepts a Fibonacci estimate (numeric point value) when the team has an estimate scale enabled.
- Cycles — the MCP can only list cycles (list_cycles), not create them. Ask the user to enable "Cycles" in Linear team settings once and create the first cycle there, then continue; issues are attached to an existing cycle via save_issue's cycle field.
Create/link the Linear Project (save_project); capture its id + url.
Push tasks.md → issues (save_issue), one per - [ ] task:
- estimate: from the task's Estimated: hint mapped to the nearest Fibonacci point; for tasks with no hint, batch-prompt once (list them, ask for points in one message) and default to unestimated if skipped.
- labels: discover, don't assume. Call list_issue_labels and map the conceptual buckets — web / agent / scaffold — onto the workspace's own labels (e.g. this workspace uses frontend / agent-eve / setup, not area:*). Derive web-vs-agent from meta.json#stack + the task's *(addressed by …)* tag; record the resolved mapping in meta.json#scrum.labels. Create a label only if no reasonable match exists.
- milestone: map epics/milestones via save_milestone when tasks.md groups by epic.
- record each task_key(line) → issue identifier for the next step.
Attach issues to the active cycle if one exists (list_cycles; the cycle itself is created in Linear per step 2 — 2-week cadence). If none exists yet, leave the issues in the backlog and note it.

Persist state:

python3 scripts/meta_linear.py <root>/.workflow/meta.json upsert-linear \
  --team-id <id> --team-name <name> --project-id <pid> --url <url>
python3 scripts/meta_linear.py <root>/.workflow/meta.json record-issues \
  --mapping '{"<task_key>":"LUC-123", ...}'

Then append a history entry via dev-flow/scripts/update_meta.py: { "skill": "linear-scrum", "action": "setup", "ran_at": "<ISO8601>" } (no phase bump).

Read the full file on GitHub · 78 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 78 lines · 185 tokens per session scan A 19e78b2bd417

Subscribe to this mod's changes

linear-scrum is a skill published in the GitHub repository lukedj78/dev-flow (5 stars, last pushed 4d ago), licensed MIT. It adds 185 tokens to every session and 1,732 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code Generation Project management agent-skills agentic-workflow ai-agents claude-code expo

agent-project-board-sync

Agent skill for project-board-sync - invoke with $agent-project-board-sync.

ruvnet/ruflo · 19 tokens

agent-issue-tracker

Agent skill for issue-tracker - invoke with $agent-issue-tracker.

ruvnet/ruflo · 21 tokens

agent-planner

Agent skill for planner - invoke with $agent-planner.

ruvnet/ruflo · 15 tokens

babysit-babysitter-issues

This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.

a5c-ai/babysitter · 69 tokens

moai-kanban-foreman

One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…

modu-ai/moai-adk · 76 tokens

taiyi-task

TaiyiForge 第5阶段 — 任务拆解，TASK.md。四端通用。.

Dong90/oh-my-taiyiforge · 24 tokens