work-breakdown

Classify project ideas by size and create Linear issues, projects, and initiatives.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mihai-chiorean/inc --skill work-breakdown-mihai-chiorean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-breakdown
Source: https://github.com/mihai-chiorean/inc/tree/main/skills/work-breakdown
Command: npx skills add https://github.com/mihai-chiorean/inc --skill work-breakdown-mihai-chiorean

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires linear-cli.

What problem does it solve?

This skill solves the ambiguity of planning large tasks by providing a structured framework to classify work size and define the necessary execution path, preventing scope creep and ensuring proper coordination.

Core Features & Use Cases

  • Work Classification: Automatically suggests a size (S/M/L/XL) based on the complexity of the user's request and specific tie-breakers.
  • Linear Orchestration: Generates the appropriate hierarchy of Linear artifacts, from single issues to initiatives, projects, and tasks.
  • Specialist Routing: Recommends relevant specialist agents (PM, tech-lead, TPM) and required planning gates (design-doc, plan-eng-review) based on the project scale.

Quick Start

Invoke the work-breakdown skill by describing your project idea to receive a classification and a structured plan for your Linear workspace.

Frequently Asked Questions about work-breakdown

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

FAQPage Schema
How do I scope and classify complex project ideas for Linear orchestration?

To scope complex project ideas for Linear orchestration, the work-breakdown skill evaluates task complexity and multi-repo coordination needs to automatically suggest a size (S/M/L/XL) and generate the appropriate Linear artifacts, preventing scope creep.

How does work classification determine Linear issue, project, and initiative hierarchy?

Work classification determines the Linear hierarchy by evaluating task complexity and applying specific tie-breakers to assign a size, which dictates whether the system generates single issues or full initiatives with projects and tasks.

Do I need the Linear CLI to classify work size and orchestrate project planning?

Yes, you need the Linear CLI installed and access to project status metadata to use this work classification and orchestration skill, ensuring consistent tracking and gate compliance across your software development planning scenarios.

What is the best way to plan cross-functional software development tasks in Linear?

The best way to plan cross-functional software development tasks in Linear is using structured work classification to recommend specialist agents (PM, tech-lead, TPM) and trigger required planning gates like design-doc or plan-eng-review based on project scale.

When should I use automated work breakdown over manual project scoping in Linear?

You should use automated work breakdown over manual project scoping in Linear when tasks require multi-repo coordination, cross-functional review, or complex execution paths that risk scope creep and need structured planning gate compliance.