| name | linear |
| description | Consolidated Linear hub for linear.app issue/project/cycle/initiative/milestone work, Linear Method planning, issue generation, search, sync, and iPix IPI-### workflows. Use whenever the user mentions Linear, linear.app, IPI-###, PLT-###, COM-###, UI-###, AI-###, DNA-###, issue, project, cycle, roadmap, milestone, backlog, or asks to create/update/search/sync Linear work. Prefer this skill over legacy linear-* skills.
|
| metadata | {"version":"1.0.0","impact":"HIGH","tags":"linear, project-management, issues, planning, ipix"} |
Linear Hub
Single entry point for Linear work in this workspace. All 14 legacy linear-* sub-skills have been folded into references/.
Operating model: keep SKILL.md as the router and hard-contract layer. Load one topic reference only when the task needs it.
When to invoke
Use this skill for any substantive Linear task:
| Trigger | Action |
|---|
IPI-###, PLT-###, COM-###, UI-###, AI-###, DNA-### | Read iPix Linear workflow first |
| Create/update/search issues, projects, cycles, milestones | Read operations |
| Plan work, write issues, scope projects, prioritize backlog | Read methodology |
| Generate issue drafts from specs, PRDs, diagrams, or notes | Read issue generator |
| Implement a Linear issue in code | Read implementation workflow |
| Sprint cycle management (status, progress, burndown, velocity) | Read sprint |
| Manage projects (CRUD, icons, leads, dates, archive) | Read projects |
| Manage project milestones (target dates, naming) | Read milestones |
| Manage sprint cycles (create, update, complete) | Read cycles |
| Manage project status updates (health, body, archive) | Read project-updates |
| Triage inbox (unassigned issues, claim, snooze) | Read triage |
| Set up automation rules and issue templates | Read automation |
| Manage labels (create, list, delete, color) | Read labels |
| Create GitHub PRs linked to Linear issues | Read pr |
| Manage Linear documents | Read documents |
| View roadmaps | Read roadmaps |
| Start/stop work, git branch, context | Read workflow |
| Search backlog/projects with safe queries | Read search |
| iPix-specific Linear contract | Read ipix |
| Templates for issues, projects, status updates, PRs | Read templates |
| Manage secrets, MCP config, API keys, CLI auth | Read security |
| Update or maintain this skill | Read skill maintenance |
Do not invoke this skill for generic product planning unless the output is meant for Linear, the iPix tracker, or an executable Linear issue.
First actions
- Classify the request: plan, generate, search, create/update, implement, or maintain.
- Read the matching reference file from the table above.
- Check available Linear access:
- Prefer the official Linear MCP server when present.
- Use Linear CLI or SDK scripts only as fallback.
- Never treat missing MCP as a blocker if CLI/SDK access works.
- For iPix issues, read the local spec in
docs/linear/issues/IPI-*-*.md when it exists before acting.
- For any create/update/delete/bulk operation, confirm only when the user intent is ambiguous, destructive, or materially different from the request.
Tool selection
| Tool path | Use when |
|---|
Official Linear MCP (mcp__linear__*) | Most reads, creates, updates, comments, project/cycle operations |
Linear CLI (linear* / linear-cli*) | MCP is unavailable or CLI output is easier to parse |
| SDK/helper scripts | Bulk operations, loops, migrations, custom transformations |
| GraphQL API | Operation is not supported by MCP/CLI/scripts |
| GitHub CLI | PR creation, PR checks, issue/PR linking when requested |
Use the actual tool names available in the current session. Do not assume a tool exists without checking.
Hard contracts
- Secrets: never expose
LINEAR_API_KEY, tokens, .env contents, or MCP config values in output.
- Deduplication: search by title/identifier before creating issues.
- Filtered reads: never fetch all team issues without filters.
- State transitions: use stable workflow state IDs when available; state names are fallback only.
- Pagination: respect cursors and limits.
- iPix traceability: every executable iPix issue should connect
IPI-###, SPEC-ID, docs/linear/issues/, todo.md, code changes, and Linear state.
- No blind automation: do not run destructive bulk updates or create PRs without explicit user intent.
- No outdated Rails-only workflow: the old
linear-implement skill referenced Rails/TDD sub-skills that do not apply to this Vite/React/Supabase repo unless the user explicitly asks for that workflow.
Reference router
| Need | Reference |
|---|
| MCP/CLI operations | operations |
| Sprint management (status, progress, burndown, velocity, carry-over) | sprint |
| Projects (CRUD, icons, dates, leads, archive) | projects |
| Milestones (create, update, target dates) | milestones |
| Cycles (create, update, complete) | cycles |
| Project updates (health status, body) | project-updates |
| Triage inbox (claim, snooze) | triage |
| Automation rules, issue templates, GitHub integration | automation |
| Labels (create, list, delete) | labels |
| GitHub PRs linked to Linear issues | pr |
| Documents (create, update, list) | documents |
| Roadmaps (view) | roadmaps |
| Start/stop work, git branch, context | workflow |
| Search backlog/projects | search |
| Issue generation (drafts, sub-issue breakdowns) | issue-generator |
| Implementation from issue to branch/PR | implementation-workflow |
| Linear Method issue/project planning | methodology |
| iPix-specific contract | ipix |
| AlwaysApply rule detail (milestones, HOLD, tool map) | governance-detail |
| Templates (issues, projects, status updates) | templates |
| Agent task_execution prepend SSOT | docs/process/templates/task-execution-prompt.md |
Output expectations
For Linear operations, report:
- What changed or was planned.
- Linear identifiers/URLs when returned by the tool.
- Any skipped actions and why.
- Follow-up commands or verification evidence.
- Next recommended step, without asking a question unless blocked.
For generated Linear content, return a ready-to-paste issue/project spec with title, description, labels, project/initiative, priority, acceptance criteria, and verification steps.
Verification patterns
Use project-specific commands from the active workspace. For iPix platform work, typical gates are:
npm run lint
npm run build
npm run test
npm run supabase:verify
npm run supabase:verify-rls
npm run supabase:verify-edge
Run only the commands relevant to the touched area. Do not run Supabase local Docker commands for iPix MVP work.
