ln-220-story-coordinator

Build IDEAL Story plans for Epics and route stories across multiple epics.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-220-story-coordinator-0xtaoist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-220-story-coordinator
Source: https://github.com/0xtaoist/taogate/tree/main/ln-220-story-coordinator
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-220-story-coordinator-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates end-to-end Epic storytelling by building an IDEAL plan (5-10 Stories) before examining existing Stories, enabling multi-epic routing and delegation to standards research, and enforcing a self-check phase.

Core Features & Use Cases

  • Decompose Epics into 5-10 Stories using a Decompose-First pattern.
  • Route Stories across multiple Epics and resolve NEEDS_NEW_EPIC when needed.
  • Delegate domain-appropriate Standards Research to ln-001 and store results in Story Technical Notes.
  • Build IDEAL Story plans, apply gating rules, and determine execution mode (CREATE/REPLAN/ADD).
  • Integrate with kanban/Linear workflows and perform self-checks after workers complete.
  • Provide a structured orchestratorBrief for the pipeline lead.

Quick Start

Provide your Epic context and IDEAL Story plan to generate or replan Epics using the coordinator.

Frequently Asked Questions about ln-220-story-coordinator

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

FAQPage Schema
How do I decompose Epics into ready-to-implement Stories?▼

To decompose Epics into ready-to-implement Stories, build an IDEAL plan of 5-10 Stories before evaluating existing ones. This Decompose-First pattern ensures vertical storytelling and applies strict gating on acceptance criteria and status rules.

What is the best way to route Stories across multiple Epics?▼

Routing Stories across multiple Epics involves evaluating your IDEAL plan against existing stories and resolving NEEDS_NEW_EPIC conditions when necessary. The coordinator determines the execution mode—CREATE, REPLAN, or ADD—to maintain kanban workflow alignment.

How does standards research integrate into Story planning?▼

Standards research integrates into Story planning through delegation to ln-001, with results stored directly in Story Technical Notes. This ensures domain-appropriate standards are applied during Phase 3 planning before Phase 5 worker delegation begins.

Do I need to provide Epic context to start Story planning?▼

You need to provide Epic context and your IDEAL Story plan to generate or replan Epics using the coordinator. This input enables automated end-to-end Story planning and supports structured orchestratorBrief generation for the pipeline lead.

Can I integrate Epic storytelling with kanban workflows?▼

You can integrate Epic storytelling with kanban workflows through Linear workflow support and self-check phases. After workers complete their tasks, the coordinator performs structured self-checks to verify acceptance criteria compliance and status rule enforcement.

Why build an IDEAL plan before examining existing Stories?▼

Building an IDEAL plan before examining existing Stories establishes a target structure of 5-10 Stories for an Epic. This prevents bias from current incomplete states and enforces strict gating on acceptance criteria during execution mode determination.