ln-400-story-executor

Orchestrate Linear or File Story workflows with prioritized task delegation and inline review.

Updated Mar 14, 2026

Search Tags:#automation #workflow #agents #story #orchestrate #task-delegation

Ready to run

npx skills add https://github.com/0xtaoist/taogate --skill ln-400-story-executor-0xtaoist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-400-story-executor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-400-story-executor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-400-story-executor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end orchestration of a Story by ordering tasks (Todo, To Rework, To Review) and delegating execution and review to specialized workers, ensuring inline review after each step.

Core Features & Use Cases

Automated task prioritization: Prioritizes To Review → To Rework → Todo, guiding the flow from planning to validation.
Delegation to specialized workers: Delegates execution to ln-401/ln-403/ln-404 and inline review to ln-402.
Immediate review after execution: Ensures that every completed task is reviewed before moving on.
Metadata-driven loading: Operates with a metadata-first approach, loading story/task metadata before full content.
Phase-driven lifecycle: Executes through defined phases (Discovery, Metadata Load, Context Review, Task Loop, Completion, Meta-Analysis) with plan-mode support.

Quick Start

Provide a story identifier to begin automated orchestration of all its tasks.

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 orchestration and delegate work to specialized agents?▼

Story task orchestration is automated by prioritizing tasks and delegating execution to specialized workers, ensuring inline review after each step. You provide a story identifier to trigger automated delegation through a phase-driven lifecycle.

What is the correct status transition when a story workflow completes task execution?▼

Story workflow status transitions to To Review after completion rather than Done. The executor enforces strict sequential reviews and controlled status transitions, ensuring every completed task moves to an inline review phase.

How does metadata-first loading work for story workflows?▼

Metadata-first loading operates by retrieving story and task metadata before fetching full content. This mechanism runs during the initial phases of the multi-phase lifecycle, optimizing context review before the task loop begins.

Can I use plan mode for story task orchestration and does it support file modes?▼

Story task orchestration supports plan mode and applies to Linear or File modes. The executor runs through defined phases like Discovery, Context Review, and Task Loop, accommodating different workflow environments.

What is the task prioritization order for story workflows?▼

Task prioritization for story workflows follows the order of To Review, To Rework, then Todo. This sequence guides the flow from initial planning through validation, ensuring completed tasks are reviewed before new ones start.