skills.rest
levnikolaevich
levnikolaevichCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ln-220-story-coordinator

Decompose Epics into 5-10 User Stories with sequential numbering.

534|73|Updated Oct 24, 2025
Search Tags:#Linear#story planning#kanban#epic#IDEAL plan#decompose-first#storying
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-220-story-coordinator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-220-story-coordinator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-220-story-coordinator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-220-story-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill creates or replans User Stories for an Epic, following a Decompose-First pattern. It builds an IDEAL Plan, then delegates work to specialized Story creators or replanners, auto-discovering team context.

Core Features & Use Cases

  • Build an IDEAL Story plan (5-10 Stories) per Epic.
  • If no existing Stories, delegate to ln-221/ln-221-story-creator for creation.
  • If Stories exist, delegate to ln-222-story-replanner to align with current Epic requirements.
  • Maintain sequential Story numbering and consistent Epic scope.

Quick Start

Use this Skill to generate or replan Stories for an Epic, following the IDEAL plan and delegation rules.

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 an Epic into User Stories?▼

Decompose an Epic into 5-10 User Stories by building an IDEAL plan first, which structures work into logical, sequential units. This Skill automates that decomposition, discovering your team context and maintaining consistent Story numbering across the Epic scope.

Can I use this to replan Stories when Epic requirements change?▼

Yes. This Skill handles both creation and replanning scenarios. When Epic requirements shift, it delegates to specialized replanners to realign existing Stories while preserving your team's numbering and scope conventions.

What's the difference between creating new Stories versus replanning existing ones?▼

Creating new Stories delegates to a Story creator when no Stories exist for an Epic. Replanning delegates to a Story replanner when Stories already exist but need realignment with updated Epic requirements.

How does this Skill integrate with Linear and kanban workflows?▼

This Skill coordinates Epic Stories within Linear-based kanban workflows by auto-discovering team context, maintaining sequential numbering, and delegating work according to your established patterns and Phase 2 standards.

What input do I need to start decomposing an Epic?▼

You need an Epic with defined requirements. This Skill auto-discovers your team context, established Story numbering conventions, and Epic scope to build an IDEAL plan without manual setup.

Does this support delegation to specialized Story workers?▼

Yes. This Skill delegates to ln-221 for Story creation or ln-222 for Story replanning based on whether Stories exist, plus ln-001 for standards research to maintain consistency.

Related Skills

Explore More Software Engineering Skills→
levnikolaevichlevnikolaevich
534

ln-200-scope-decomposer

Decompose initiative scope into Epics and Stories via ln-210 and ln-220.

Community
Advanced
cbbkrd-techcbbkrd-tech

ln-222-story-replanner

Replan Linear stories by comparing ideal plans against existing stories.

Community
Advanced
mcauduro0mcauduro0
1

ln-300-task-coordinator

Analyze Story requirements and delegate task creation or replanning to specialized workers.

Community
Advanced
cbbkrd-techcbbkrd-tech

ln-200-scope-decomposer

Decompose initiatives into Epics, Stories, and RICE prioritization.

Community
Advanced