ln-410-story-executor

Orchestrate end-to-end Story execution with task delegation and quality gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates an entire Story by looping through its tasks in priority order (To Review, To Rework, Todo) and delegating to specialized workers. It coordinates quality gates and ensures story-level progress is tracked and reported back to Story quality gates.

Core Features & Use Cases

  • Load Story metadata (without full task descriptions) and drive execution across its child tasks.
  • Delegate each task to the appropriate executor or rework/review workflow, ensuring status transitions are correct.
  • Trigger Story quality gates (Pass 1 then Pass 2) and iterate if new tasks are created.
  • Maintain foundation-first flow and keep kanban/story state in sync with the orchestrator.

Quick Start

Use this Skill to execute a Story end-to-end; it will coordinate per-task execution, hand-offs to reviewers, and gating via ln-500-story-quality-gate.

Frequently Asked Questions about ln-410-story-executor

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

FAQPage Schema
How do I orchestrate story execution across multiple tasks and workflow states?

Story orchestration coordinates task execution through priority-ordered delegation (To Review, To Rework, Todo states) to specialized workers, triggering quality gates and maintaining kanban status transitions end-to-end. It loops through child tasks, enforces phase-gated execution from discovery through quality validation, and prevents bulk updates.

What's the difference between delegating individual tasks versus bulk story updates?

Task delegation enforces single-task assignment with immediate follow-on quality checks, foundation-first flow, and metadata-driven planning phases. Bulk updates bypass per-task validation and phase sequencing, risking incomplete discovery and premature rework cycles.

How do quality gates work in story execution workflows?

Quality gating runs two-pass validation (Pass 1, then Pass 2) after task completion, assesses story-level progress, optionally revalidates if new tasks are created, and feeds results back to coordinate rework or progression to done state.

Can I automate task delegation and quality assessment across story kanban boards?

Automation routes tasks through specialized executors based on priority and state, applies continuous quality assessment without manual intervention, coordinates reviewer hand-offs, and syncs kanban updates with orchestration progress automatically.

What metadata does story orchestration require before execution starts?

Story orchestration loads metadata without full task descriptions during Phase 2, using priority tags, state labels, and phase markers to drive phase-gated execution, quality gate triggers, and delegation decisions across the workflow.

When should I use story orchestration instead of manual task management?

Use orchestration for multi-phase story flows requiring consistent quality gates, priority-based delegation, state-transition tracking, and automated reviewer coordination. Manual management suits single-task workflows or ad-hoc processes without repeatable phases.