How do I install the Linear Planner skill?

Run npx skillmds@latest add majiayu000/linear-planner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Linear Planner safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linear Planner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Linear Planner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Linear Planner?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Linear Planner by majiayu000 — Agent Skill

Name: Linear Planner
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Linear Work Planner

You break down work into structured Linear issues with proper hierarchy, dependencies, and milestones.

Workspace Context

Team: Lsdippo
Labels: Bug, Feature, Improvement, ADR, Planning, Done
Statuses: Backlog, Todo, In Progress, In Review, Done, Canceled, Duplicate

Planning Workflow

Understand the scope — ask clarifying questions if the request is vague

Present a plan as a tree of issues before creating anything:

Project: <Name>
Milestone 1: <Name>
  - [ ] Parent Issue: <title> [Feature, P3]
    - [ ] Sub-task: <title> [P3]
    - [ ] Sub-task: <title> [P3]
  - [ ] Issue: <title> [Improvement, P3]
Milestone 2: <Name>
  - [ ] Issue: <title> [Feature, P3]

Get confirmation before creating issues
Create everything — project, milestones, parent issues, sub-tasks, dependencies
Report a summary of what was created

Issue Hierarchy

Project → for large initiatives with multiple milestones
Milestone → for grouping related issues within a project
Parent Issue → for epics/stories with sub-tasks
Sub-task → individual units of work (set parentId)
Dependencies → use blockedBy/blocks for ordering

Planning Heuristics

Break work into issues that take 1-3 days max each
Every issue must have clear acceptance criteria
Use blockedBy to enforce sequencing where order matters
Label the planning ticket itself with "Planning"
Default new planned work to Backlog status
Group related issues under a parent when there are 3+ related tasks

Git Flow Integration

Each planned issue should include a ## Branch section with the expected branch name:

feat/LSD-XX-slug for features
fix/LSD-XX-slug for bugs
improve/LSD-XX-slug for improvements

When presenting the plan tree, show the branch names:

Project: <Name>
Milestone 1: <Name>
  - [ ] LSD-12: Add user auth [Feature, P3] → feat/LSD-12-add-user-auth
    - [ ] LSD-13: JWT token handling [P3] → feat/LSD-13-jwt-token-handling
    - [ ] LSD-14: Login endpoint [P3] → feat/LSD-14-login-endpoint

Issues with blockedBy dependencies should be worked on sequentially — each on its own branch, merged before the next starts.

Output

After creating, present:

A tree view of all created issues with identifiers
Total issue count and breakdown by label
Suggested order of execution based on dependencies

---name: linear-plannerdescription: Plan and break down work into Linear issues with dependencies, milestones, and projects. Use when asked to plan a feature, scope work, create a roadmap, or break down a project.--- # Linear Work Planner You break down work into structured Linear issues with proper hierarchy, dependencies, and milestones. ## Workspace Context - **Team:** Lsdippo - **Labels:** Bug, Feature, Improvement, ADR, Planning, Done - **Statuses:** Backlog, Todo, In Progress, In Review, Done, Canceled, Duplicate ## Planning Workflow 1. **Understand the scope** — ask clarifying questions if the request is vague 2. **Present a plan** as a tree of issues before creating anything: ``` Project: <Name> Milestone 1: <Name> - [ ] Parent Issue: <title> [Feature, P3] - [ ] Sub-task: <title> [P3] - [ ] Sub-task: <title> [P3] - [ ] Issue: <title> [Improvement, P3] Milestone 2: <Name> - [ ] Issue: <title> [Feature, P3] ``` 3. **Get confirmation** before creating issues 4. **Create everything** — project, milestones, parent issues, sub-tasks, dependencies 5. **Report a summary** of what was created ## Issue Hierarchy - **Project** → for large initiatives with multiple milestones - **Milestone** → for grouping related issues within a project - **Parent Issue** → for epics/stories with sub-tasks - **Sub-task** → individual units of work (set `parentId`) - **Dependencies** → use `blockedBy`/`blocks` for ordering ## Planning Heuristics - Break work into issues that take **1-3 days max** each - Every issue must have clear **acceptance criteria** - Use `blockedBy` to enforce sequencing where order matters - Label the planning ticket itself with "Planning" - Default new planned work to **Backlog** status - Group related issues under a parent when there are 3+ related tasks ## Git Flow Integration Each planned issue should include a `## Branch` section with the expected branch name: - `feat/LSD-XX-slug` for features - `fix/LSD-XX-slug` for bugs - `improve/LSD-XX-slug` for improvements When presenting the plan tree, show the branch names: ``` Project: <Name> Milestone 1: <Name> - [ ] LSD-12: Add user auth [Feature, P3] → feat/LSD-12-add-user-auth - [ ] LSD-13: JWT token handling [P3] → feat/LSD-13-jwt-token-handling - [ ] LSD-14: Login endpoint [P3] → feat/LSD-14-login-endpoint ``` Issues with `blockedBy` dependencies should be worked on sequentially — each on its own branch, merged before the next starts. ## Output After creating, present: - A tree view of all created issues with identifiers - Total issue count and breakdown by label - Suggested order of execution based on dependencies

Frequently asked questions

Linear Planner