ln-300-task-coordinator

Orchestrate Story task planning and delegate to creation or replanning workers.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-300-task-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-300-task-coordinator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-300-task-coordinator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-300-task-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates creation or replanning of implementation tasks for a Story. It auto-discovers team context, builds an IDEAL plan (1-6 tasks), and delegates to creation or replanning workers while standardizing the foundation-first approach.

Core Features & Use Cases

  • Auto-discover Team ID and load Story context (AC, Technical Notes, Context).
  • Build an IDEAL plan with 1-6 implementation tasks in Foundation-First order.
  • Delegate to ln-301-task-creator (CREATE/ADD) or ln-302-task-replanner (REPLAN) based on mode.
  • Strip Non-Functional Requirements and ensure tasks reflect current functional scope.
  • Verify results via updated Kanban and provide next steps.

Quick Start

Run the orchestrator to decompose a Story into a concrete IDEAL plan and route tasks to the appropriate worker.

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 break down a story into implementation tasks?

Task decomposition organizes a story into 1-6 concrete implementation tasks ordered by foundation-first dependency. This Skill auto-discovers team context, loads story requirements and technical notes, builds an IDEAL plan excluding tests and refactoring, then delegates task creation to workers—stripping non-functional requirements to keep scope focused on functional delivery.

What's the difference between creating new tasks and replanning existing ones?

CREATE mode generates fresh implementation tasks from a story; REPLAN mode adjusts an existing task sequence. This Skill detects the mode automatically, routes to the appropriate worker (ln-301-task-creator or ln-302-task-replanner), and updates kanban status to reflect the current plan state.

Can I use this to delegate tasks across a team?

Yes. The Skill auto-discovers your Team ID, orchestrates task routing to specialized workers, handles payload construction with correct formatting, enables auto-approval, and reports kanban updates—so your team receives well-decomposed, foundation-first tasks ready for execution.

How does foundation-first task ordering work?

Foundation-first orders implementation tasks by dependency: shared infrastructure and core utilities come first, then features that depend on them. This Skill builds IDEAL plans following that sequence, ensuring workers tackle tasks in the right order and avoiding blocked or circular dependencies.

What story context does the coordinator need?

The Skill loads Acceptance Criteria, Technical Notes, and Story Context automatically. It uses these to build a task plan aligned with functional and technical requirements, then strips non-functional requirements to keep tasks lean and delivery-focused.

How many tasks should an IDEAL plan contain?

An IDEAL plan contains 1–6 implementation tasks. This range balances concrete execution granularity with planning overhead, ensuring tasks stay actionable while capturing the story's full functional scope.