linear-planner

Name: linear-planner
Availability: InStock
Author: LSDIPPOLLC

Transform feature scope into sequenced Linear issues with hierarchy and dependencies.

Updated Mar 12, 2026

Search Tags:#dependencies #acceptance criteria #linear #milestones #roadmapping #git branching #issue planning

Ready to run

npx skills add https://github.com/LSDIPPOLLC/ai-orchestration --skill linear-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linear-planner
Source: https://github.com/LSDIPPOLLC/ai-orchestration/tree/main/.claude/skills/linear-planner
Command: npx skills add https://github.com/LSDIPPOLLC/ai-orchestration --skill linear-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the chaos of turning a vague request into actionable, ordered work by producing a structured set of Linear issues tied together by projects, milestones, dependencies, and acceptance criteria.

Core Features & Use Cases

Tree-based planning: Presents a hierarchical plan (project → milestone → parent issue → sub-tasks) before creating anything.
Dependency-aware sequencing: Uses dependency relationships to enforce an execution order.
Issue quality guardrails: Enforces short issue scope (1–3 days), requires clear acceptance criteria, and labels the planning ticket with Planning.
Git-branch conventions: Includes a required ## Branch section so each planned issue maps to an expected branch name format.

Quick Start

Ask the skill to plan a feature and specify what you want to accomplish, for example: “/linear-planner build an authentication system for the web app with JWT login and secure token handling.”

Frequently Asked Questions about linear-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn vague feature requests into a sequenced Linear roadmap?▼

To turn vague requests into a sequenced Linear roadmap, you can scope initiatives into epics, milestones, and sub-tasks, establishing execution order and dependencies for actionable project tracking.

What is the best way to plan Linear issues with dependencies and milestones?▼

The best way to plan Linear issues with dependencies is to generate a hierarchical plan tree, linking parent issues to sub-tasks through dependency relationships to enforce a strict execution order.

How do I add git branching conventions to my Linear issue planning?▼

You can add git branching conventions to Linear issue planning by defining a required Branch section within each issue, mapping expected branch name formats directly to their corresponding planned tasks.

Does Linear issue planning work for scoping large initiatives into sub-tasks?▼

Yes, Linear issue planning works for scoping large initiatives by breaking down project scopes into structured hierarchies of epics, parent issues, and manageable sub-tasks before any creation occurs.

How do I enforce acceptance criteria and issue scope limits in Linear?▼

To enforce acceptance criteria and issue scope limits in Linear, apply planning guardrails that require clear completion conditions and restrict individual issue scope to an estimated one to three days of work.

When should I not use a dependency-aware plan tree for Linear roadmapping?▼

You should not use a dependency-aware plan tree for Linear roadmapping when your project lacks clear hierarchical structures, or when tasks are simple enough that defining strict milestones and execution order creates unnecessary overhead.