LSDIPPOLLC/linear-planner
.claude/skills/linear-planner/SKILL.md
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.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add LSDIPPOLLC/ai-orchestration linear-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:34 PM4.7s1 file scanned
SKILL.md
- name:
- linear-planner
- description:
- 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.
- user-invocable:
- true
- argument-hint:
- <what to plan>
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/blocksfor ordering
Planning Heuristics
- Break work into issues that take 1-3 days max each
- Every issue must have clear acceptance criteria
- Use
blockedByto 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-slugfor featuresfix/LSD-XX-slugfor bugsimprove/LSD-XX-slugfor 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
Related Skills
LSDIPPOLLC/ralph-wiggum-pm
development
VerifiedTrustedCommunity
Ralph Wiggum: Project Manager — Continuous ticket consumption, code review, and work generation loop. Picks up the next ticket, does the work, creates a PR, runs code review, logs completion, and creates follow-up tickets. Use when asked to start the loop, consume tickets, or grind through work.
SKILL.mdUpdated Apr 16, 2026
LSDIPPOLLC/linear-triage
testing
VerifiedTrustedCommunity
Triage and review Linear issues - list, filter, prioritize, and update issue status. Use when asked to check tickets, review backlog, or see what needs doing.
SKILL.mdUpdated Apr 16, 2026
LSDIPPOLLC/linear-create
tools
VerifiedTrustedCommunity
Create new Linear issues for bugs, features, improvements, or tasks. Use when asked to file a ticket, log work, track a task, or create an issue.
SKILL.mdUpdated Apr 16, 2026
LSDIPPOLLC/linear-adr
testing
VerifiedTrustedCommunity
Create and manage Architecture Decision Records (ADRs) as Linear issues and documents. Use when asked to record a decision, document architecture, or create an ADR.
SKILL.mdUpdated Apr 16, 2026