ln-300-task-coordinator

Analyze Story requirements and delegate task creation or replanning to specialized workers.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-300-task-coordinator-mcauduro0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-300-task-coordinator
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-300-task-coordinator
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-300-task-coordinator-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating or updating implementation tasks for a Story, ensuring optimal planning and delegation to specialized workers.

Core Features & Use Cases

  • Automated Task Planning: Analyzes Story requirements (AC, Technical Notes) to build an ideal, Foundation-First task plan.
  • Intelligent Delegation: Detects whether to create new tasks or replan existing ones, routing requests to ln-301-task-creator or ln-302-task-replanner respectively.
  • Use Case: When a new feature Story is defined, this Skill automatically breaks it down into manageable implementation tasks, assigns them an execution order, and prepares them for creation in Linear. If requirements change, it replans the existing tasks to match the updated Story.

Quick Start

Use the ln-300-task-coordinator skill to create implementation tasks for a new story.

Frequently Asked Questions about ln-300-task-coordinator

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

FAQPage Schema
How do I automate story decomposition into implementation tasks for Linear?

Story decomposition is automated by analyzing Story requirements and breaking them down into an optimal, Foundation-First task plan. The process extracts functional scope from acceptance criteria and technical notes, then translates it into actionable implementation tasks.

What is the best way to replan existing agile tasks when story requirements change?

Replanning existing tasks is handled by routing modified story requirements to a specialized replanner worker. This updates the current task execution order and content to match the updated functional scope without duplicating or overwriting unrelated workflow items.

How does task orchestration work for new feature stories?

Task orchestration works by detecting user intent and the presence of existing tasks, then delegating creation or modification to specialized worker skills. This ensures new feature stories are automatically broken down, assigned an execution order, and prepared for Linear.

Do I need existing tasks in my workflow to use automated task planning?

Existing tasks are not required to use automated task planning. The orchestration logic detects whether to create new tasks for a fresh story or replan existing ones, intelligently routing requests to the appropriate worker skill based on your current state.

Can I use workflow automation to assign execution order to implementation tasks?

Workflow automation assigns execution order by building an optimal, Foundation-First task plan from analyzed story requirements. This ensures manageable implementation tasks are created sequentially and prepared for creation in Linear.

Why does my task plan only include functional scope from the story?

Task plans only include functional scope because the orchestration logic specifically translates actionable implementation requirements into tasks. Non-functional metadata or general story descriptions are filtered out to ensure optimal planning and delegation.