Does this skill create test or refactoring tasks?

No, this specific skill focuses exclusively on functional implementation tasks. Test tasks and refactoring tasks are handled by separate specialized planners later in the workflow.

What is Foundation-First ordering?

It is a logical execution sequence that ensures backend dependencies (Database and Repositories) are built before the services, APIs, and frontend components that rely on them.

Can I use this without a Linear account?

Yes. If the skill does not detect a Linear setup, it automatically switches to File Mode, managing your tasks via Markdown files in your project's docs directory.

What is the maximum number of tasks it will create per story?

The orchestrator is capped at 6 implementation tasks per story to ensure work remains manageable and focused, typically aiming for 3-5 hour increments per task.

Linear Task Planner (Orchestrator)

Name: Linear Task Planner (Orchestrator)
Author: levnikolaevich

bylevnikolaevich

•

Collaboration Tools

Orchestrates the planning, creation, and reorganization of technical implementation tasks for software development stories.

About

The ln-300-task-coordinator is a sophisticated orchestration skill designed to bridge the gap between high-level user stories and actionable development tasks. It analyzes story requirements, technical notes, and acceptance criteria to build an optimal execution plan consisting of 1-6 implementation tasks following a 'Foundation-First' methodology. Whether operating in Linear Mode via MCP or File Mode for local documentation, it intelligently detects whether to create new tasks or replan existing ones, delegating execution to specialized worker skills while ensuring strict adherence to project architecture and dependency management.

Key Features

Auto-discovery of Team IDs and Story context from project files
Foundation-First Planning (DB → Repository → Service → API → Frontend)
Automatic Story Decomposition into 1-6 scoped implementation tasks
Dual-mode support for Linear MCP or local Markdown task tracking
38 GitHub stars
Intelligent mode detection for Creating, Adding, or Replanning tasks

Use Cases

Breaking down a complex feature story into sequential, developer-ready technical tasks
Maintaining a structured kanban board or task directory without manual data entry
Updating and replanning task lists when project requirements or acceptance criteria change

About

Key Features

Auto-discovery of Team IDs and Story context from project files
Foundation-First Planning (DB → Repository → Service → API → Frontend)
Automatic Story Decomposition into 1-6 scoped implementation tasks
Dual-mode support for Linear MCP or local Markdown task tracking
38 GitHub stars
Intelligent mode detection for Creating, Adding, or Replanning tasks

Use Cases

Breaking down a complex feature story into sequential, developer-ready technical tasks
Maintaining a structured kanban board or task directory without manual data entry
Updating and replanning task lists when project requirements or acceptance criteria change