ln-400-story-executor

Prioritize and delegate Story tasks to worker skills for execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end execution of Story tasks, ensuring they are processed in the correct priority and delegated to the appropriate workers, streamlining the development workflow.

Core Features & Use Cases

  • Automated Task Prioritization: Processes tasks in a strict order: To Review, To Rework, then Todo.
  • Branch Management: Automatically creates and checks out feature branches for each Story.
  • Delegation to Workers: Intelligently dispatches tasks to specialized executor and reviewer skills.
  • Use Case: When a Story is in the 'Todo' or 'In Progress' state, this Skill can be invoked to manage the entire task execution and review cycle, moving the Story towards completion.

Quick Start

Use the ln-400-story-executor skill to begin orchestrating tasks for story PROJ-42.

Frequently Asked Questions about ln-400-story-executor

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

FAQPage Schema
How do I automate story task execution and code review workflows?

Story task execution is automated by prioritizing tasks and delegating them to specialized worker skills for sequential or parallel processing. The workflow automatically manages branch setup, loads task metadata, and ensures immediate code review upon completion before updating the story status.

What is the best way to orchestrate agile development tasks across multiple workers?

Orchestrating agile development tasks involves dispatching items in a strict priority order: To Review, To Rework, then Todo. The system intelligently delegates tasks to specialized executor and reviewer skills, managing both sequential and parallel execution based on defined task groups to move stories toward completion.

Can I automatically create feature branches when starting story execution?

Feature branch creation is handled automatically during story execution setup. The workflow creates and checks out a dedicated branch for each story before loading task metadata and dispatching any items to worker skills, ensuring isolated development environments for the automated execution cycle.

Does story execution support parallel task processing for developer productivity?

Story execution supports parallel task processing by grouping tasks based on defined metadata criteria. Tasks within the same group can run concurrently across worker skills, while groups themselves execute sequentially, optimizing developer productivity without violating task dependency constraints.

Why does my task execution workflow prioritize rework items before new todo tasks?

Task execution workflows prioritize rework items to resolve existing review feedback before starting new development. This strict processing order—To Review, To Rework, then Todo—prevents backlog accumulation and ensures stories move toward completion with immediate post-execution reviews.

When should I not use automated task orchestration for story execution?

Automated task orchestration is not suited for stories lacking defined task groups or metadata for worker delegation. If tasks require manual branching, lack clear priority states like To Review or Todo, or need human intervention during execution, this automated workflow approach will not yield reliable completion status updates.