ln-400-story-pipeline

Orchestrate Linear Story workflows from planning to completion via specialized workers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates the complete Story workflow from planning to Done, delegating to specialized workers.

Core Features & Use Cases

  • Orchestrates phase 1-4: discovery, planning, execution, completion
  • Delegates tasks to ln-300, ln-310, ln-410, ln-500
  • Automatic Story finalization through quality gate

Quick Start

Launch the story pipeline to process an existing Epic.

Frequently Asked Questions about ln-400-story-pipeline

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

FAQPage Schema
How do I orchestrate an end-to-end story processing workflow in Linear?

Story orchestration automates the complete workflow from task discovery through completion. This Skill orchestrates phases 1–4 (discovery, planning, execution, completion) by delegating specialized work to task coordination, validation, execution, and quality-gate workers, then reloads Story and Tasks after each phase.

Can I automate task planning and execution for existing Linear stories?

Yes. The orchestration pipeline processes stories already in Linear by auto-discovering Team ID from your kanban board metadata, loading story and task details, and delegating work through specialized coordinators and validators that execute and verify tasks end-to-end.

What does the story pipeline do after task execution completes?

After execution, the pipeline runs final verification through a quality gate worker that validates task completion, then automatically finalizes the story. The workflow loops through discovery, planning, execution, and verification until all tasks reach Done status.

How does the orchestration handle story and task metadata during processing?

The pipeline loads only essential metadata (id, title, status, labels) from Linear stories and reloads both Story and Tasks state after each worker completes its phase, ensuring downstream workers operate on current data.

What's required before running the story pipeline on a Linear workspace?

Stories must already exist in Linear (e.g., US001, API-53) and your kanban board metadata must be stored in docs/tasks/kanban_board.md so the pipeline can auto-discover your Team ID and begin orchestration.

Does story orchestration work for Epics and complex multi-task stories?

Yes. The pipeline orchestrates complete workflows for stories of any complexity by delegating task coordination, validation, and execution to specialized workers that handle discovery, planning, and quality verification in sequence.