ln-300-task-coordinator

Decompose user stories into 1-8 foundation-first implementation tasks with verification methods.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-300-task-coordinator-dorrio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-300-task-coordinator
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-300-task-coordinator
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-300-task-coordinator-dorrio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you break down a user story into an optimal, actionable plan of implementation tasks, ensuring a structured and efficient development process before any code is written.

Core Features & Use Cases

  • Story Decomposition: Divides complex stories into 1-8 manageable implementation tasks.
  • Foundation-First Ordering: Organizes tasks logically, starting with foundational elements like database and backend before moving to UI.
  • Clear Verification: Each task includes a defined method for verifying its completion against acceptance criteria.
  • Use Case: When starting a new feature like "Implement user profile editing," this skill will generate a plan including tasks for database schema updates, API endpoint creation, and UI component development.

Quick Start

Use the ln-300-task-coordinator skill to plan the tasks for the story about user authentication.

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 user story into implementation tasks for agile development?

Story breakdown decomposes a user story into an optimal execution plan of 1 to 8 implementation tasks. It organizes tasks foundation-first, ensuring a structured development process before coding begins.

What is the best way to order story tasks for workflow automation?

Ordering story tasks foundation-first ensures foundational elements like database and backend are built before UI components. This logical sequence creates an actionable implementation plan for efficient development.

How do I verify task completion when planning an implementation plan?

Task verification requires defining a clear, measurable outcome and a specific verification method like a test, command, or inspect action for each task. This ensures completion against acceptance criteria.

Can I use story breakdown to update my kanban board automatically?

Story breakdown updates the Kanban board as the single source of truth during task planning. It ensures task independence while maintaining an accurate visual workflow for agile development.

Does task planning work for complex features needing database and API tasks?

Task planning handles complex features by dividing them into manageable implementation tasks. For a feature like user profile editing, it generates tasks for database schema updates, API endpoints, and UI components.

Why should I limit story breakdown to 8 implementation tasks?

Limiting story breakdown to 1 to 8 implementation tasks ensures stories remain manageable and actionable. This constraint maintains task independence and focus within the execution plan.